Deployed cda5933 with MkDocs version: 1.6.0

androidx_test/index.html

@@ -1904,7 +1904,7 @@ <h1 id="androidx-test">AndroidX Test</h1>
 test. Furthermore it will make your tests more portable and compatible with our future plans.</p>
 <h3 id="testrunner">TestRunner</h3>
 <p>It is now possible to use the AndroidX test runner in Robolectric tests. If you require a custom test runner currently,
-please check out the new <a href="../javadoc/latest/org/robolectric/pluginapi/package-summary.html">configuration and plugin API</a>
+please check out the new <a href="javadoc/latest/org/robolectric/pluginapi/package-summary.html">configuration and plugin API</a>
 and let us know if there are any extension points missing that you require.</p>
 <p><strong>Robolectric</strong>
 <div class="language-kotlin highlight"><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a><span class="nd">@RunWith</span><span class="p">(</span><span class="n">RobolectricTestRunner</span><span class="o">::</span><span class="n">class</span><span class="p">)</span>

blog/2019/06/04/paused-looper/index.html

@@ -2017,7 +2017,7 @@ <h2 id="solution">Solution</h2>
 PAUSED mode vs the existing ‘LEGACY’ mode include:</p>
 <ul>
 <li>Tasks posted to the main looper are not automatically executed inline. Similar to the
-<a href="../../../../../javadoc/4.3/org/robolectric/util/Scheduler.IdleState.html#PAUSED"> legacy paused IdleState</a>, 
+<a href="../../javadoc/4.3/org/robolectric/util/Scheduler.IdleState.html#PAUSED"> legacy paused IdleState</a>, 
 tasks posted to the main looper must be explicitly executed via <code>ShadowLooper</code> APIs. However, 
 we’ve made a couple additional improvements in PAUSED mode that make this easier:</li>
 <li>Robolectric will warn users if a test fails with unexecuted tasks in the main looper queue. 

configuring/index.html

@@ -1983,7 +1983,7 @@
 <h1 id="configuring-robolectric">Configuring Robolectric</h1>
 <p>Several aspects of Robolectric's behavior can be configured at runtime, using <code>robolectric.properties</code> files for package-level configuration, or <code>@Config</code> annotations for class-level or method-level configuration.</p>
 <h3 id="config-annotation"><code>@Config</code> Annotation</h3>
-<p>To configure Robolectric for a single test class or method, use the <a href="../javadoc/latest/org/robolectric/annotation/Config.html"><code>@Config</code></a> annotation. The annotation can be applied to classes and methods; values specified at the method level will override values specified at the class level.</p>
+<p>To configure Robolectric for a single test class or method, use the <a href="javadoc/latest/org/robolectric/annotation/Config.html"><code>@Config</code></a> annotation. The annotation can be applied to classes and methods; values specified at the method level will override values specified at the class level.</p>
 <p>Base classes are also searched for annotations, so if you find yourself specifying the same values on a large number of tests, you can create a base class and move your <code>@Config</code> annotation to that class.</p>
 <div class="language-java highlight"><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a><span class="w">  </span><span class="nd">@Config</span><span class="p">(</span><span class="n">sdk</span><span class="o">=</span><span class="n">KITKAT</span><span class="p">,</span>
 </span><span id="__span-0-2"><a id="__codelineno-0-2" name="__codelineno-0-2" href="#__codelineno-0-2"></a><span class="w">      </span><span class="n">shadows</span><span class="o">=</span><span class="p">{</span><span class="n">ShadowFoo</span><span class="p">.</span><span class="na">class</span><span class="p">,</span><span class="w"> </span><span class="n">ShadowBar</span><span class="p">.</span><span class="na">class</span><span class="p">})</span>

device-configuration/index.html

@@ -2052,7 +2052,7 @@ <h2 id="changing-device-configuration">Changing Device Configuration</h2>
 </span><span id="__span-2-9"><a id="__codelineno-2-9" name="__codelineno-2-9" href="#__codelineno-2-9"></a><span class="p">}</span>
 </span></code></pre></div>
 <p>The string parameter to <code>setQualifiers()</code> has the same rules as <code>Config.qualifiers</code>.</p>
-<p>Note that <code>RuntimeEnvironment.setQualifiers()</code> updates the system and application resources with the new configuration, but does not trigger any action on extant activities or other components. <a href="../javadoc/latest/org/robolectric/android/controller/ActivityController.html#configurationChange(android.content.res.Configuration)"><code>ActivityController.configurationChange()</code></a> can be used to simulate the sequence of events that take place on a device when its configuration changes.</p>
+<p>Note that <code>RuntimeEnvironment.setQualifiers()</code> updates the system and application resources with the new configuration, but does not trigger any action on extant activities or other components. <a href="javadoc/latest/org/robolectric/android/controller/ActivityController.html#configurationChange(android.content.res.Configuration)"><code>ActivityController.configurationChange()</code></a> can be used to simulate the sequence of events that take place on a device when its configuration changes.</p>
 <p>If the activity is configured to handle the configuration changes, <code>ActivityController.configurationChange()</code> will call the activity’s <code>onConfigurationChanged()</code> method. If not, <code>ActivityController</code> destroys and recreates the activity.</p>
 <h2 id="simulating-displays">Simulating Displays</h2>
 <p>Robolectric allows display properties to be changed during a test using setters on <code>ShadowDisplay</code>. For Jelly Bean MR1 and up, multiple displays can be simulated using APIs on <code>ShadowDisplayManager</code>. See their documentation for more details.</p>