TestClassExecutionEventGeneratorTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Start migrating test classes to the most appropriate subproject

Story: gradle/langos#103

Item: refactor-plugins

    • -131
    • +0
    ./TestClassExecutionEventGeneratorTest.groovy
  1. … 124 more files in changeset.
Moved TimeProvider and impl from core to baseServices project.

    • -1
    • +1
    ./TestClassExecutionEventGeneratorTest.groovy
  1. … 49 more files in changeset.
Moved IdGenerator and implementations from core to baseServices.

    • -2
    • +2
    ./TestClassExecutionEventGeneratorTest.groovy
  1. … 53 more files in changeset.
Better handle a broken JUnit test Runner, so that the failures end up in the test results, rather than as a nasty stacktrace on the console: - If a failure happens instantiating the Runner, or during Runner.run() and no tests are running, then add a synthetic broken 'initializationError' test. - If a failure happens during Runner.run() and some tests are running, then attach the failure to those tests. - Extracted TestClassExecutionEventGenerator our of JUnitTestClassExecuter, and did some renaming.

    • -0
    • +131
    ./TestClassExecutionEventGeneratorTest.groovy
  1. … 10 more files in changeset.