Skip to content

Releases: cqse/teamscale-jacoco-agent

v30.1.1

25 Jul 09:42
Compare
Choose a tag to compare
  • [fix] teamscale-gradle-plugin: Warnings were logged during test execution (WARNING: JAXBContext implementation could not be found. WADL feature is disabled., WARNING: A class javax.activation.DataSource for a default provider)

v30.1.0

17 Jul 14:56
Compare
Choose a tag to compare
  • [feature] The option tiamode has now an additional choice disk to dump testwise coverage as JSON to the output folder.
  • [feature] teamscale-maven-plugin: The configuration options runAllTests, runImpacted, and tiamode are now available
  • [fix] impacted-test-engine: Mixed test results for dynamically generated tests were incorrectly summarized
  • [fix] The option ignore-uncovered-classes did not filter out empty interface nodes from the XML report
  • [fix] teamscale-gradle-plugin: The plugin failed to log the No class files found in the given directories! error message

v30.0.2

10 May 13:03
Compare
Choose a tag to compare
  • [fix] teamscale-gradle-plugin: Reports uploaded by teamscaleReportUpload ended up in wrong partition
  • [fix] impacted-test-engine: Failure when no tests were impacted

v30.0.1

08 May 09:20
Compare
Choose a tag to compare
  • [fix] report-generator: Fixed Gradle module metadata which resulted in Could not find org.jacoco.agent-0.8.8-runtime

v30.0.0

03 May 13:43
Compare
Choose a tag to compare
  • [breaking change] teamscale-maven-plugin: Made plugin compatible with surefire 3.0.0. Replace the teamscale-surefire-provider dependency with impacted-test-engine in your pom.xml files.
  • [feature] teamscale-gradle-plugin, teamscale-maven-plugin: Added ability to pass excluded test engines to impacted test engine
  • [fix] teamscale-maven-plugin: Testwise coverage uploads were performed per test cluster instead of one upload after all tests
  • [fix] teamscale-gradle-plugin, teamscale-maven-plugin: Impacted tests were requested once for each test engine
  • [fix] teamscale-gradle-plugin, teamscale-maven-plugin: Execution of impacted tests failed when test names were unstable i.e. parameterized tests with parameters that are not serializeable

v29.1.3

28 Feb 09:27
2946037
Compare
Choose a tag to compare
  • [fix] http control server was not correctly shut down after the tests ended

v29.1.2

08 Feb 18:17
Compare
Choose a tag to compare
  • [fix] teamscale-maven-plugin: Partition was not correctly provided to the impacted test engine
  • [fix] tia-client: Semicolons in test names were not correctly sent to the Teamscale JaCoCo Agent

v29.1.1

07 Feb 12:03
Compare
Choose a tag to compare
  • [fix] teamscale-gradle-plugin, teamscale-maven-plugin, teamscale-jacoco-agent: Tooling did not provide a way to set the partial flag

v29.1.0

02 Feb 10:12
Compare
Choose a tag to compare
  • [feature] teamscale-gradle-plugin: Allow parallel test execution with testwise coverage collection
  • [fix] teamscale-gradle-plugin: Verify that maxParallelForks is 1
  • [fix] impacted-test-engine: Provide sane fallback for non-supported test engines

v29.0.0

31 Jan 07:40
Compare
Choose a tag to compare
  • [fix] Fixed the prefix extraction pattern and the partition pattern for Artifactory in the agent's documentation
  • [fix/breaking change] teamscale-client, teamscale-gradle-plugin, teamscale-maven-plugin, teamscale-jacoco-agent: Teamscale 8.0 introduced the concept of execution units. To distinguish them from normal, singular test executions, the -test-exection- and -execution-unit- uniform path prefixes were introduced. This broke gradle and maven test runner plugins because the actual test paths and Teamscale's uniform paths did not match anymore. To prevent this, testName is now exposed by the teamscale client and used by the plugins which corresponds to the uniform path without the prefixes. If you're using the client, or listen to the /testrun/start API from the Teamscale JaCoCo agent, this is a breaking change. You now need to use testName in your runner, not the uniformPath.