CaptureTestOutputTestResultProcessorTest.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

    • -104
    • +0
    ./CaptureTestOutputTestResultProcessorTest.groovy
  1. … 124 more files in changeset.
Busted complexity to separate classes to simplify testing and kill a shamock test I contributed when I was young and stupid

    • -65
    • +58
    ./CaptureTestOutputTestResultProcessorTest.groovy
  1. … 3 more files in changeset.
Fixed an issue in our test infrastructure related to not passing correct test id for onOuput events. Previously, only the suite id was passed when the test triggered any output events. Now we're passing the correct test id. Now it is possible to improve the visual side of printing standard streams from tests. It is one of the acceptance criteria for the 'show standard streams for tests' story.

    • -4
    • +50
    ./CaptureTestOutputTestResultProcessorTest.groovy
  1. … 2 more files in changeset.
GRADLE-1009 [Tidying up things after adding test output listener]. Refactoring, rename job wrt output listener / test output event

    • -3
    • +3
    ./CaptureTestOutputTestResultProcessorTest.groovy
  1. … 14 more files in changeset.
GRADLE-1009 [Tidying up things after adding test output listener]. Now the output listener provides information whether the message is std out or std err.

    • -2
    • +3
    ./CaptureTestOutputTestResultProcessorTest.groovy
  1. … 8 more files in changeset.
Renamed subprojects/gradle-(.+) to subprojects/$1

    • -0
    • +64
    ./CaptureTestOutputTestResultProcessorTest.groovy
  1. … 6178 more files in changeset.