Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make sure that we have a separate report directory for each binary variant of the component under test

Story: gradle/langos#113

    • -3
    • +5
    ./fixtures/DefaultTestExecutionResult.groovy
  1. … 3 more files in changeset.
Changing PollingConditions.poll() usages to ConcurrentTestUtil.poll()

+review REVIEW-5540

  1. … 13 more files in changeset.
Fixing issue with change from milliseconds to seconds in URLvalidator

+review REVIEW-5510

  1. … 4 more files in changeset.
Adding tooling tests for play continuous build

+review REVIEW-5510

  1. … 7 more files in changeset.
Added integration test for Play multiproject sample

  1. … 2 more files in changeset.
Simplified construction of JUnitXmlTestExecutionResult in tests

    • -1
    • +1
    ./fixtures/DefaultTestExecutionResult.groovy
    • -14
    • +9
    ./fixtures/JUnitXmlTestExecutionResult.groovy
  1. … 2 more files in changeset.
Changing UrlValidator to verify text and binary files differently. Moved TextUtil to base-services so it can be used from internal-testing.

+review REVIEW-5272

  1. … 6 more files in changeset.
Fixing windows CI failure for play custom fixture

  1. … 1 more file in changeset.
Fixing windows CI failure for play custom fixture

Fixing windows CI failure for play custom fixture

Adding play coffeescript assets to customPlayApp test fixture.

+review REVIEW-5272

  1. … 5 more files in changeset.
Adding play content testing to existing play run tests. -Temporarily disabled advanced sample content test until sporadic compile issues can be cleared up.

+review REVIEW-5272

  1. … 8 more files in changeset.
Cleaning up play sample integration tests and addressing timeout issues.

+review REVIEW-5272

  1. … 1 more file in changeset.
fix ci errors

- update path assertions in test cases

+review REVIEW-5263

    • -5
    • +7
    ./fixtures/JUnitXmlTestExecutionResult.groovy
  1. … 3 more files in changeset.
Stop PlayRun task gracefully

- listening for ctrl+d input to stop the play application

- open issues:

- integration tests not running in daemon mode as DisconnectableInputStream reads input eagerly.

- should have central place for dealing with userinput (probably a later story)

- currently daemons InputForwarder stops forwarding after receiving ctrl+d command, means

that after stopping the PlayRun task using ctrl+d no other stdin of a build is forwarded

TODO:

- verify behaviour on windows

+review REVIEW-5261

  1. … 7 more files in changeset.
Fail test execution when non-default config failure policy is used with a TestNG version that doesn't support it

+review REVIEW-5274

    • -0
    • +5
    ./fixtures/DefaultTestExecutionResult.groovy
    • -3
    • +14
    ./fixtures/HtmlTestExecutionResult.groovy
    • -0
    • +13
    ./fixtures/JUnitTestClassExecutionResult.groovy
    • -0
    • +2
    ./fixtures/TestClassExecutionResult.java
  1. … 5 more files in changeset.
try stabelizing play-run integration test for daemon test executor

+review REVIEW-5261

  1. … 1 more file in changeset.
avoid sleeps in SonarRunnerSmokeIntegrationTest

+review REVIEW-5170

    • -0
    • +35
    ./fixtures/UrlValidator.groovy
  1. … 2 more files in changeset.
Modified JUnitTestClassExecutionResult to support the changes made in JUnitXmlResultWriter.

- Overloaded `assertTestCount` with a 4 integer function that asserts the skip count.

- Changed assert methods to filter on the existence(or not) of a `skipped` sub-element.

- Added an assert to the checking method to check that there is a skipped annotation and that is not empty.

- Removed findIgnoredTests as it is no longer required.

    • -8
    • +16
    ./fixtures/JUnitTestClassExecutionResult.groovy
Changed some int tests to use DefaultTestExecutionResult rather than JUnitTestExecutionResult, to use whatever the default mechanism for verifying test results happens to be.

    • -1
    • +1
    ./fixtures/DefaultTestExecutionResult.groovy
    • -8
    • +11
    ./fixtures/HtmlTestExecutionResult.groovy
  1. … 23 more files in changeset.
GRADLE-2730 Added an integ test.

    • -0
    • +5
    ./fixtures/JUnitTestClassExecutionResult.groovy
  1. … 1 more file in changeset.
Changed the HtmlTestExecutionResult assert methods so that they actually assert stuff, and some other minor fixes in the various TestExecutionResult implementations.

    • -2
    • +5
    ./fixtures/DefaultTestExecutionResult.groovy
    • -23
    • +25
    ./fixtures/HtmlTestExecutionResult.groovy
  1. … 2 more files in changeset.
Changed the profile and test reports to generate only the index page into the destination directory, and the other stuff ends up in sub-directories.

    • -2
    • +2
    ./fixtures/HtmlTestExecutionResult.groovy
  1. … 18 more files in changeset.
Moved some classes out of org.gradle.util.

    • -1
    • +1
    ./fixtures/HtmlTestExecutionResult.groovy
  1. … 63 more files in changeset.
REVIEW-3092: moved toSafeFileName method to baseServices - avoids duplicate code in test fixtures - REVIEW-3090 encode # as well - REVIEW-3092 add testcoverage for toSafeFileName

    • -25
    • +3
    ./fixtures/HtmlTestExecutionResult.groovy
  1. … 7 more files in changeset.
Add a bit more coverage to the cucumberjvm test and fix xml test result fixture.

    • -1
    • +1
    ./fixtures/HtmlTestExecutionResult.groovy
    • -2
    • +2
    ./fixtures/JUnitXmlTestExecutionResult.groovy
  1. … 1 more file in changeset.
fix html report generation for test class names that contains spaces, slashes and other non supported chars in filenames

    • -1
    • +24
    ./fixtures/HtmlTestExecutionResult.groovy
  1. … 5 more files in changeset.
Fix xml test result generation for cucumber tests. We now take care of generating correct filenames used in xml reports; TODO: Do the same for html

    • -2
    • +8
    ./fixtures/JUnitXmlTestExecutionResult.groovy
  1. … 3 more files in changeset.
Improve assertions on JUnit XML output to test that no system-out type elements are present when not using test case output association.

    • -4
    • +3
    ./fixtures/JUnitTestClassExecutionResult.groovy
Enabled generating the JUnit XML file with output per test case.

This is not complete. The actual generation of the XML based on the TestResultsProvider is unit tested and there is functional level coverage when running TestNG tests.

Coverage for JUnit is needed, as well as coverage at the intermediary parts of the results/report generation.

There are also some types to tidy up.

    • -0
    • +8
    ./fixtures/DefaultTestExecutionResult.groovy
    • -0
    • +9
    ./fixtures/HtmlTestExecutionResult.groovy
    • -0
    • +161
    ./fixtures/JUnitTestClassExecutionResult.groovy
    • -116
    • +7
    ./fixtures/JUnitXmlTestExecutionResult.groovy
    • -0
    • +4
    ./fixtures/TestClassExecutionResult.java
    • -0
    • +22
    ./fixtures/TestResultOutputAssociation.java
  1. … 12 more files in changeset.