Skip to content

Commit

Permalink
Remove hardcoded references to robolectric.org
Browse files Browse the repository at this point in the history
  • Loading branch information
MGaetan89 committed Apr 15, 2024
1 parent 29bc871 commit 067b26e
Show file tree
Hide file tree
Showing 6 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion _posts/2018-10-25-robolectric-4-0.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ android.enableUnitTestBinaryResources=true

### Migration Tool

Robolectric 4.0 contains a number of API changes that may require modifications to your test code. Check out the [migration notes](http://robolectric.org/migrating/#migrating-to-40) and use the new [automated migration tool](http://robolectric.org/automated-migration/) to help convert your existing tests to be compatible with Robolectric 4.0.
Robolectric 4.0 contains a number of API changes that may require modifications to your test code. Check out the [migration notes](migrating.md/#migrating-to-40) and use the new [automated migration tool](automated-migration.md) to help convert your existing tests to be compatible with Robolectric 4.0.

### Release Notes

Expand Down
2 changes: 1 addition & 1 deletion _posts/2019-06-04-paused-looper.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ PAUSED mode vs the existing ‘LEGACY’ mode include:


* Tasks posted to the main looper are not automatically executed inline. Similar to the
[ legacy paused IdleState](http://robolectric.org/javadoc/4.3/org/robolectric/util/Scheduler.IdleState.html#PAUSED),
[ legacy paused IdleState](javadoc/4.3/org/robolectric/util/Scheduler.IdleState.html#PAUSED),
tasks posted to the main looper must be explicitly executed via `ShadowLooper` APIs. However,
we’ve made a couple additional improvements in PAUSED mode that make this easier:
* Robolectric will warn users if a test fails with unexecuted tasks in the main looper queue.
Expand Down
2 changes: 1 addition & 1 deletion _posts/2021-10-06-sharedTest.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ There are some Google's projects have used sharedTest pattern to sharing test co
[accompanist: [All] Share tests to run on Robolectric & Emulators by chrisbanes][10]

[1]: https://medium.com/androiddevelopers/write-once-run-everywhere-tests-on-android-88adb2ba20c5 "Write Once, Run Everywhere Tests on Android"
[2]: http://robolectric.org/blog/2018/10/25/robolectric-4-0/ "Robolectric 4.0 release"
[2]: {{ site_url }}blog/2018/10/25/robolectric-4-0/ "Robolectric 4.0 release"
[3]: https://developer.android.com/training/testing/junit-runner "AndroidJUnit4 test runner"
[4]: https://developer.android.com/training/testing/espresso/ "Espresso"
[5]: https://developer.android.com/reference/androidx/test/core/app/ActivityScenario "ActivityScenario"
Expand Down
4 changes: 2 additions & 2 deletions _posts/2023-11-11-improving-android-all-downloading.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ testOptions {
}
```

[Robolectric's configuration documentation](https://robolectric.org/configuring/) contains a detailed description
[Robolectric's configuration documentation](configuring.md) contains a detailed description
of these special Robolectric properties, and you can read it for more details.

## Leveraging Robolectric's offline mode
Expand Down Expand Up @@ -163,7 +163,7 @@ your git repository might become bigger and bigger. If you like this approach,
you can store android-all jars in an external repository like
[AndroidX](https://android-review.googlesource.com/c/platform/prebuilts/androidx/external/+/2813314).

[Robolectric's configuring documentation](https://robolectric.org/configuring/) contains
[Robolectric's configuring documentation](configuring.md) contains
a detailed description of these special Robolectric properties, and you can
read it for details.

Expand Down
2 changes: 1 addition & 1 deletion docs/contributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Robolectric uses javadoc to document API's behavior. There are special rules for
* All visible non-`@Implementation` methods SHOULD have descriptive Javadoc.
* Don't write javadoc comments like "Shadow for (whatever).". The javadoc will appear in a section clearly related to testing, so make it make sense in context.

Robolectric will release javadoc at robolectric.org after every main version released. For example, Robolectric's {{ robolectric.version.current }} javadoc is released at {{ site_url }}javadoc/{{ robolectric.version.current }}/.
Robolectric will release javadoc at {{ site_url }} after every main version released. For example, Robolectric's {{ robolectric.version.current }} javadoc is released at {{ site_url }}javadoc/{{ robolectric.version.current }}/.

### Deprecations and Backwards Compatibility

Expand Down
2 changes: 1 addition & 1 deletion docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ hide:

Running tests on an Android emulator or device is slow! Building, deploying, and launching the app often takes a minute or more. That's no way to do <abbr title="Test-Driven Development">TDD</abbr>. There must be a better way.

[Robolectric](http://robolectric.org/) is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM on your workstation in seconds. With Robolectric you can write tests like this:
[Robolectric]({{ site_url }}) is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM on your workstation in seconds. With Robolectric you can write tests like this:

```java
@RunWith(RobolectricTestRunner.class)
Expand Down

0 comments on commit 067b26e

Please sign in to comment.