JUnitIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Renamed subprojects/gradle-(.+) to subprojects/$1

  1. … 6178 more files in changeset.
GRADLE-1279 - Don't attempt to execute tests on non-static inner classes.

  1. … 2 more files in changeset.
GRADLE-974/GRADLE-1208 - Handle cases where there might be multiple failures for a given test: @Before and @After methods both fail, or @Test and @After methods both fail, multiple @After methods fail, etc.

  1. … 12 more files in changeset.
GRADLE-1242 - Handle case where junit test calls TestCase.setName() on itself.

  1. … 5 more files in changeset.
GRADLE-1090 - java plugin provides defaults for Test task instances

  1. … 6 more files in changeset.
GRADLE-680 - Treat test task as out-of-date when the set of selected tests changes - Treat test task as out-of-date when selected test framework changes - Moved handling of -Dtest.single and -Dtest.debug out of Test into JavaBasePlugin and added some int test coverage - Merged TestFramework and TestFrameworkInstance - Extracted the bulk of Test.executeTests() into a TestExecuter.

  1. … 37 more files in changeset.
Fixed case where a junit test failure was discarded when the test failure exception's toString() method throws an exception.

  1. … 4 more files in changeset.
- Use test failure exception's toString() rather then getMessage() in the junit report

  1. … 2 more files in changeset.
GRADLE-945 - Added int test coverage for a bunch of different ways that junit tests can fail.

  1. … 8 more files in changeset.
GRADLE-942 - Rearranged some of the logging system, so that LoggingManager is used to add stdout and stderr listeners - Changed GradleDistributionExecuter to assert that there are no stack traces in Gradle std output or std error when running int tests

  1. … 31 more files in changeset.
- Shuffled a bunch of classes around.

  1. … 135 more files in changeset.
GRADLE-926 - Don't block waiting for other test processes to complete when reforking a test process.

  1. … 25 more files in changeset.
- Ignore 'downloading' messages in actual user guide sample output. - Moved int test fixtures into separate package - GradleDistribution no longer provides an executer - Changed QuickGradleExecuter into a junit rule - Int tests that extend AbstractIntegrationTest use the same user homd dir and default-import as int tests that @RunWith(DistributionIntegrationTestRunner) - Fixed ui:integTest to actually run the tests

  1. … 110 more files in changeset.
- Distinguish between internal (Gradle) failures and failures from the suite itself. Log internal failures as errors with stack trace. - Reorganised responsibilities of JUnitTestClassExecuter and JUnitTestResultProcessorAdapter

  1. … 14 more files in changeset.
GRADLE-907 - Fix to include output of java util logging used by classes under test in the test report.

  1. … 25 more files in changeset.
GRADLE-907 - Replaced usage of Ant's JunitTestRunner with our own, to improve error handling and get better access to stdout capturing. - Refactored JUnitTestResult test fixtures - Fixed test class/name detection for early 4.x versions

  1. … 49 more files in changeset.
- Roll back handling for when test installs a SecurityManager

  1. … 6 more files in changeset.
- better handle the case where a test installs a SecurityManager

  1. … 5 more files in changeset.
- Use a junit @Rule to inject the GradleDistribution into each integration test, rather than a home-made injection mechanism - Use a custom runner for the user guide samples integration test, which runs each sample as a separate test - Temporarily switched off expected and action output checking for int tests, as it wasn't actually checking anything and some tests are currently broken. Will switch it on again soon.

  1. … 48 more files in changeset.
- Added an int test to check non-abstract superclasses can be excluded when running tests

  1. … 1 more file in changeset.
- Renamed apply url: to apply from: - Renamed apply id: to apply plugin: - Renamed apply type: to apply plugin:

  1. … 97 more files in changeset.
- Removed BootstrapUtil, it is no longer used - Renamed some worker process classes

  1. … 25 more files in changeset.
GRADLE-800 - Changed test execution to load classes under test using test process' system classloader, rather than an isolated classloader

  1. … 34 more files in changeset.
GRADLE-800 - Report only failed test classes, not each failed test (ie the behaviour we used to have when using the Ant task) - Fail the build if any test suite fails (eg a failure in a JUnit Runner implementation) - Be a bit more forgiving of badly behaved test processors

  1. … 11 more files in changeset.
GRADLE-800 - Renamed AntTest back to Test - Renamed Test to TestDescriptor

  1. … 45 more files in changeset.
GRADLE-800 - Added Test.parent - Added TestResult.testCount, successfulTestCount, failedTestCount, skippedTestCount

  1. … 9 more files in changeset.
GRADLE-800 - Provide correct resultType for test suite result - Collect failures in the test suite itself to provide in the result. - Send less stuff across the wire for test results - Added JUnitTestResult fixture to use in int tests

  1. … 43 more files in changeset.
GRADLE-800 - Added a TestResult parameter to TestListener.afterSuite(), currently always has success status. - Added JavaForkOptions.enableAssertions, defaults to true for AntTest. - Ensure every Test instance has a unique id. - Synthesise a test suite for each worker process.

  1. … 48 more files in changeset.
GRADLE-800 - Set context classloader when executing tests - Merged TestSuite into Test - Changed TestListenerFormatter and TestNGListenerAdapter to handle parallel test execution - Use internal interface TestResultProcessor, rather than public TestListener, to ship test events around

  1. … 42 more files in changeset.
GRADLE-800 Fleshed out TestListener events: - Use a consistent cross-framework naming scheme for tests - Can get class name and method name for a test, if applicable - TestSuite is-a composite Test - Fire a global suite start and end event that encloses all tests and suites - Added start and end times to TestResult.

  1. … 23 more files in changeset.