Commits on Feb 27, 2017

1. Support the selection of a default Runner in ClassRequest …

   This patch updates `Request` and `ClassRequest` to enable the configuration of a default JUnit4 Runner other than `BlockJUnit4ClassRunner`. The only visible change is a new static method in Request, `classWithDefaultRunner`, which configures the runner class to use if not configured in the test.
   
   The context of this change is the following: when managing a large test suite that gets contributions from a large development team, it's typical to enforce certain logic across all tests for global state initialization and cleanup. In the particular case of Twitter for Android, all our tests set up global application graphs before test execution and reset static state afterwards. It is critical for correctness that every single test follows this pattern. This seems to be a particular example of the general need for a mechanism that configures the global state of the test environment.
   
   This is typically achieved by forcing all tests to use a single shared runner or to extend a base class. However, these approaches are error prone, since they require dilligence for setting up the test correctly, or an external validation (eg. a checkstyle detector). A default test runner is a low-tech solution to this problem: a test runner extending `BlockJUnit4ClassRunner` implements state management logic and is configured to be used with all tests that don't explicitly say otherwise.
   
    The change is incomplete and doesn't implement tests, and it's meant a small proof of concept for feedback.

   César Puerta committed Feb 27, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for a63079d
   • Browse repository at this point

   Copy the full SHA

   a63079d View commit details

   Browse the repository at this point in the history