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

    • -80
    • +0
    ./AttachParentTestResultProcessorTest.groovy
    • -347
    • +0
    ./StateTrackingTestResultProcessorTest.groovy
  1. … 122 more files in changeset.
Introduce TestListenerInternal, use this as the canonical way of receiving test events. Adapt TestListener and TestOutputListener to this internal type.

    • -0
    • +347
    ./StateTrackingTestResultProcessorTest.groovy
    • -324
    • +0
    ./TestListenerAdapterTest.groovy
  1. … 10 more files in changeset.
Remove @author tags and names from source code.

- Added checkstyle check for @author

- Added not to CONTRIBUTING.md saying that we don't use names in the codebase

  1. … 1213 more files in changeset.
redesign of test logging

- all logging options are declared in org.gradle.api.tasks.testing.logging.TestLogging

- TestLogging options can be varied per log level

  1. … 30 more files in changeset.
polishing

    • -11
    • +13
    ./TestListenerAdapterTest.groovy
renamed class TestSummaryListener to TestProgressLogger

    • -0
    • +118
    ./TestProgressLoggerTest.groovy
    • -118
    • +0
    ./TestSummaryListenerTest.groovy
  1. … 2 more files in changeset.
improvements to TestLogger

- renamed to TestCountLogger

- show skipped tests

- slightly rephrased output

- make logger remember whether root suite reported failure (shift responsibility from TestSummaryListener)

    • -0
    • +151
    ./TestCountLoggerTest.groovy
  1. … 2 more files in changeset.
Reworked a bit fix for GRADLE-2035 (test execution failures)...

In case we receive output event for a test that is completed we use the parent test descriptor to describe the output. We do it all the way to the root. If no descriptor is found we return UnknownTestDescriptor. However, this should never happen because when the suite is completed we have already stopped capturing output.

  1. … 1 more file in changeset.
GRADLE-2035 Fixed the "couldn't find test with id" problem...

Apparently, we can receive an output event for a test that we already received a complete event. However, I couldn't reproduce it in an integration test nor in local testing (I've generated hundreds of test classes, each with good number of test methods and ran it in various ways but the problem was not exposed). So, it's still a working theory. Also, we should peer review this implementation and try to find a much better solution.

    • -12
    • +31
    ./TestListenerAdapterTest.groovy
  1. … 4 more files in changeset.
Refactored jmock -> spock before adding more changes to the class

    • -136
    • +118
    ./TestSummaryListenerTest.groovy
Rename job after the code review. Renamed the implementation class from XxxImpl -> DefaultXxx

  1. … 4 more files in changeset.
GRADLE-1009 [Tidying up things after adding test output listener]. Added more coverage & refactorings

  1. … 2 more files in changeset.
GRADLE-1009 [Tidying up things after adding test output listener]. Started passing the test descriptor to the output listener. This way the client will know for what test the output event was sent.

  1. … 4 more files in changeset.
GRADLE-1009 [Tidying up things after adding test output listener]. Refactoring, rename job OutputListener -> TestOutputListener

  1. … 5 more files in changeset.
GRADLE-1009 [Tidying up things after adding test output listener]. Refactoring, rename job wrt output listener / test output event

  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.

  1. … 8 more files in changeset.
GRADLE-1009. Added some unit test coverage

GRADLE-1009. Some cleanup. Refactored the rest of the jmock test.

    • -67
    • +37
    ./TestListenerAdapterTest.groovy
GRADLE-1009. Some cleanup. Refactoring old jmock test into Spock. Minor refactorings on the way. Few tests still left...

    • -0
    • +48
    ./DefaultTestResultTest.groovy
    • -261
    • +114
    ./TestListenerAdapterTest.groovy
  1. … 5 more files in changeset.
First stab at GRADLE-1009. The implementation is very simple - added a new listener that is notified in case of output. TODO: JMock test :) and few other things.

  1. … 4 more files in changeset.
GRADLE-1417 - Reworked progress logging, so that better event descriptions are delivered to tooling api clients. - Refactored ProgressLogger, to make some implicit behaviour a bit more explicit, and to allow callers more control over how events are reported.

  1. … 21 more files in changeset.
Renamed subprojects/gradle-(.+) to subprojects/$1

    • -0
    • +80
    ./AttachParentTestResultProcessorTest.groovy
    • -0
    • +413
    ./TestListenerAdapterTest.groovy
    • -0
    • +134
    ./TestLoggerTest.groovy
    • -0
    • +136
    ./TestSummaryListenerTest.groovy
  1. … 6175 more files in changeset.