diff --git a/docs/blog/posts/2017-03-01-hermetic-builds.md b/docs/blog/posts/2017-03-01-hermetic-builds.md index e83e73d05..0e020e3e0 100644 --- a/docs/blog/posts/2017-03-01-hermetic-builds.md +++ b/docs/blog/posts/2017-03-01-hermetic-builds.md @@ -11,8 +11,6 @@ slug: hermetic-builds Robolectric needs access to multiple Android SDK jars in order to perform its magic, which means it needs special configuration beyond just setting up dependencies in your build. By default, it tries to download Android SDK jars from Maven Central. - - But what if you have a [hermetic build environment](http://blog.fahhem.com/2013/12/hermetic-build-systems/)? You just need to do a little more configuration. Here's a Gradle build script that'll help: diff --git a/docs/blog/posts/2017-03-02-robolectric-3-3-and-roadmap.md b/docs/blog/posts/2017-03-02-robolectric-3-3-and-roadmap.md index 21081f25f..af1f470b7 100644 --- a/docs/blog/posts/2017-03-02-robolectric-3-3-and-roadmap.md +++ b/docs/blog/posts/2017-03-02-robolectric-3-3-and-roadmap.md @@ -10,8 +10,6 @@ slug: robolectric-3-3-and-roadmap Your Robolectric maintainers are pleased to announce the release of [Robolectric 3.3](https://github.com/robolectric/robolectric/releases/tag/robolectric-3.3)! There's been a bunch of activity recently in Robolectric, and we wanted to give a quick update on our thinking about where the project is going. - - ### Introduction Robolectric started life in 2010 as a quick hack to allow Android tests to be run on a regular JVM rather than a device or emulator, allowing for fast [TDD cycles](https://en.wikipedia.org/wiki/Test-driven_development#Test-driven_development_cycle). It was mostly developed in brief spurts as needed for testing specific projects. diff --git a/docs/blog/posts/2017-11-13-resources-for-real.md b/docs/blog/posts/2017-11-13-resources-for-real.md index 35766547c..c96749821 100644 --- a/docs/blog/posts/2017-11-13-resources-for-real.md +++ b/docs/blog/posts/2017-11-13-resources-for-real.md @@ -11,8 +11,6 @@ slug: resources-for-real Up until now, Robolectric has relied on rough approximations of the Android framework's resource handling logic, backwards-engineered to be 'good enough' for many testing purposes. - - We've gotten to the point where 'good enough' is no longer good enough. We've completely reimplemented Robolectric's resources system, transliterating the real native Android resource handling code from the original C++ to Java, and in the coming several releases we'll be rolling it out. The new code will fix numerous bugs in the old Robolectric simulation, which we expect will expose places where your tests rely on incorrect Robolectric behavior. We're doing this in three separate releases to give you a chance to fix your tests in smaller batches. We strongly recommend you apply each upgrade individually and watch the release notes for migration hints. diff --git a/docs/blog/posts/2018-05-09-robolectric-4-0-alpha.md b/docs/blog/posts/2018-05-09-robolectric-4-0-alpha.md index c71deb835..98569ea99 100644 --- a/docs/blog/posts/2018-05-09-robolectric-4-0-alpha.md +++ b/docs/blog/posts/2018-05-09-robolectric-4-0-alpha.md @@ -11,8 +11,6 @@ slug: robolectric-4-0-alpha The Robolectric team is super excited to announce the first alpha release of Robolectric 4.0, as well as some new developments in the world of Robolectric and Android testing in general. - - ### `androidx.test` We’re collaborating closely with the Android Jetpack testing team to develop common APIs for writing Android tests that can run as both local (JVM-based) and on-device (instrumentation) tests. From 4.0 on, Robolectric will support Jetpack’s [androidx.test](https://developer.android.com/training/testing/) APIs, starting with support for the [`AndroidJUnit4` test runner](https://developer.android.com/training/testing/junit-runner), [`ActivityTestRule`](https://developer.android.com/training/testing/junit-rules), and [Espresso](https://developer.android.com/training/testing/espresso/) for interacting with UI components. diff --git a/docs/blog/posts/2018-10-25-robolectric-4-0.md b/docs/blog/posts/2018-10-25-robolectric-4-0.md index b60b96256..cc369e630 100644 --- a/docs/blog/posts/2018-10-25-robolectric-4-0.md +++ b/docs/blog/posts/2018-10-25-robolectric-4-0.md @@ -11,8 +11,6 @@ slug: robolectric-4-0 Robolectric 4.0 is released! Here's what's new! - - ### `androidx.test` The different idioms for testing using Robolectric and instrumentation tests has long been a headache. With today's release of Robolectric 4.0 and `androidx.test` 1.0.0, both testing environments are converging on a set of common test APIs. Robolectric now supports the [`AndroidJUnit4` test runner](https://developer.android.com/training/testing/junit-runner), [`ActivityTestRule`](https://developer.android.com/training/testing/junit-rules), and [Espresso](https://developer.android.com/training/testing/espresso/) for interacting with UI components. diff --git a/docs/blog/posts/2019-06-04-paused-looper.md b/docs/blog/posts/2019-06-04-paused-looper.md index 7e8a88faf..b4298af15 100644 --- a/docs/blog/posts/2019-06-04-paused-looper.md +++ b/docs/blog/posts/2019-06-04-paused-looper.md @@ -12,8 +12,6 @@ slug: paused-looper more realistic.** Try it out today by annotating your tests with _@LooperMode(PAUSED)_ and let us know your experience! - - ## Background Unlike on a real device, Robolectric shares a single thread for both UI operations and Test code. diff --git a/docs/blog/posts/2021-09-13-a-memorial-tribute-for-jonathan-gerrish.md b/docs/blog/posts/2021-09-13-a-memorial-tribute-for-jonathan-gerrish.md index 05934598c..b075c605e 100644 --- a/docs/blog/posts/2021-09-13-a-memorial-tribute-for-jonathan-gerrish.md +++ b/docs/blog/posts/2021-09-13-a-memorial-tribute-for-jonathan-gerrish.md @@ -17,8 +17,6 @@ contributor since 2014. He saw incredible potential in Robolectric and championed it within Google, elevating it to an officially supported testing tool that grew to be used by tens of thousands of Android developers. - - The breadth of the contributions that Jonathan made to the project are too wide to list in this post. He was involved in many high-profile projects such as revamping PackageManager support and binary resources. He also worked diff --git a/docs/blog/posts/2021-10-06-sharedTest.md b/docs/blog/posts/2021-10-06-sharedTest.md index f48a14069..914e7dcee 100644 --- a/docs/blog/posts/2021-10-06-sharedTest.md +++ b/docs/blog/posts/2021-10-06-sharedTest.md @@ -9,8 +9,6 @@ slug: sharedTest After [Robolectric's 4.0 release][2], Robolectric supports the [`AndroidJUnit4` test runner][3], [`ActivityScenario`][5], and [Espresso][4] for interacting with UI components. As we know, we also can run those tests with an official emulator. This article will show an often overlooked but widely-used pattern called sharedTest to share tests between local and instrumentation tests. This will provide the benefit of fast unit testing while ensuring that tests are high-fidelity by enabling them to be run in an emulator. - - ## Using sharedTest steps by steps The first thing that sharedTest needs is [`AndroidJUnit4` test runner][3]. It is a test runner that supports both Robolectric and [`androidx.test`][13]. There is a sample class, called [`SampleFragmentTest.kt`][14] from [FragmentScenarioSample][15] that uses [`AndroidJUnit4` test runner][3]: diff --git a/docs/blog/posts/2022-09-06-Umesh-GSoC-on-ConscryptMode.md b/docs/blog/posts/2022-09-06-Umesh-GSoC-on-ConscryptMode.md index b25c23233..5bba5b3a5 100644 --- a/docs/blog/posts/2022-09-06-Umesh-GSoC-on-ConscryptMode.md +++ b/docs/blog/posts/2022-09-06-Umesh-GSoC-on-ConscryptMode.md @@ -9,8 +9,6 @@ slug: Umesh-GSoC-on-ConscryptMode My name is [Umesh Singh](https://github.com/Umesh-01) and I was an open source contributor through Google Summer of Code this year. Google Summer of Code (GSoC) is a program where external participants can contribute to an open source project over a few months. We learn new computer science concepts, how to work on open source repositories, and create real code contributions to projects! - - My project was `Switching Robolectric from BouncyCastle to Conscrypt as the default security provider`. Robolectric was using [BouncyCastle](https://www.bouncycastle.org/) as the Java Cryptography Extension (JCE) security provider. After the introduction of Android P, Android switched to using [Google Conscrypt](https://source.android.com/docs/core/architecture/modular-system/conscrypt) as the security provider. To be more consistent with Android, Robolectric needed to be updated to use Conscrypt as the default security provider. diff --git a/docs/blog/posts/2023-11-11-improving-android-all-downloading.md b/docs/blog/posts/2023-11-11-improving-android-all-downloading.md index c82faa50f..bcc5da13c 100644 --- a/docs/blog/posts/2023-11-11-improving-android-all-downloading.md +++ b/docs/blog/posts/2023-11-11-improving-android-all-downloading.md @@ -10,8 +10,6 @@ slug: improving-android-all-downloading In recent years, the team has received multiple issues regarding Robolectric's inability to download/resolve the necessary android-all jars when running Robolectric tests in a CI environment. Some examples include: - - 1. [android-all not downloaded as part of robolectric, or is it a separate dependency?](https://github.com/robolectric/robolectric/issues/7886) 2. [Robolectric failing because not downloading dependencies in Jenkins when using Artifactory](https://github.com/robolectric/robolectric/issues/8158) diff --git a/docs/blog/posts/2024-02-25-robolectric-2024-gsoc.md b/docs/blog/posts/2024-02-25-robolectric-2024-gsoc.md index 350af112a..9917acc12 100644 --- a/docs/blog/posts/2024-02-25-robolectric-2024-gsoc.md +++ b/docs/blog/posts/2024-02-25-robolectric-2024-gsoc.md @@ -12,8 +12,6 @@ organization for the Google Summer of Code (GSOC) 2024! This will provide an opportunity for students interested in Android development to contribute to one of the most widely used testing frameworks for Android. - - ### What is Robolectric? For those new to Robolectric, it's a powerful testing framework that allows diff --git a/mkdocs.yml b/mkdocs.yml index 862778cf0..f933f40d1 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -54,7 +54,6 @@ markdown_extensions: plugins: - blog: categories: false - post_excerpt: required post_excerpt_max_authors: 5 - macros: on_error_fail: true diff --git a/overrides/partials/post.html b/overrides/partials/post.html new file mode 100644 index 000000000..462cb7290 --- /dev/null +++ b/overrides/partials/post.html @@ -0,0 +1,105 @@ + + + +
+
+ + + {% if post.authors %} + + {% endif %} + + +
+
    + + +
  • + + {#- Collapse whitespace -#} +
    • + + + {% if post.categories %} +
  • + {{ lang.t("blog.categories.in") }} + {% for category in post.categories %} + + {{- category.title -}} + + {%- if loop.revindex > 1 %}, {% endif -%} + {% endfor -%} +
    • + {% endif %} + + + {% if post.config.readtime %} + {% set time = post.config.readtime %} +
  • + {% if time == 1 %} + {{ lang.t("readtime.one") }} + {% else %} + {{ lang.t("readtime.other") | replace("#", time) }} + {% endif %} +
    • + {% endif %} +
+ + + {% if post.config.draft %} + + {{ lang.t("blog.draft") }} + + {% endif %} +
+
+ + +
+ + {% set post_content = post.md.convert(post.markdown) %} + + {{ post_content.split("

", 1)[0] }}

+ + + + {% if post.more %} + + {% endif %} +
+