AbstractGradleVsMavenPerformanceTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Execute performance test scenarios on a fresh working copy

Reusing whatever state the last test left behind can make performance

seem better (because of preexisting caches) or worse (because of lots of output).

This makes the results dependent on the order in which the tests are executed.

It also prevented us from using incremental build for the project templates.

We now create a fresh copy of the template project for each test run,

fixing both of these problems at once.

    • -0
    • +1
    ./AbstractGradleVsMavenPerformanceTest.groovy
  1. … 14 more files in changeset.
Move all result-related classes to org.gradle.performance.results

    • -0
    • +2
    ./AbstractGradleVsMavenPerformanceTest.groovy
  1. … 55 more files in changeset.
Extract performance test fixtures to separate project

    • -0
    • +67
    ./AbstractGradleVsMavenPerformanceTest.groovy
  1. … 248 more files in changeset.