v15.0.0

• [feature] support for git.properties to supply commit information
• [breaking change] Agent now ignores SSL certificates by default and only turns on validation if
  validate-ssl=true is passed in the agent arguments. Existing setups will continue to work but
  validation will be disabled from this version on
• [fix] Agent uses higher timeouts (20s) for all HTTP connections to account for slow networks

v14.0.0

• [fix] Reduced memory requirements for generating testwise coverage.
• [breaking change] When using the convert tool in --testwise-coverage mode the new --split-after 5000 option will break up testwise coverage files automatically after the specified number of tests written. This ensures that generated reports are small enough to be uploaded to Teamscale. Default is 5000. The given output file will now be appended suffixed -1, -2 etc.. If the specified output file is named testwise_coverage.json the actually written file will be called testwise_coverage-1.json for the first 5000 tests. For uploading multiple files use an upload session.

v13.0.1

[fix] Prevent -1 to show up as covered line in Testwise Coverage report

v13.0.0

• [feature] added dump-on-exit option
• [breaking change] added mode option (Must be set for Testwise Coverage mode. http-server-port or test-env alone is no longer sufficient)
• [feature] The agent now optionally accepts test execution results via /test/end
• [feature] Support for Java 12

v12.0.0

• [breaking change] The convert tool now uses wildcard patterns for the class matching (was ant pattern before)
• [breaking change] The agent returns the correct 204 and 400 status codes in Testwise Coverage mode

v11.2.0

[feature] The agent now also supports Java 11 code.

v11.0.4

• [breaking change] Test impact mode no longer uploads reports to teamscale and does no longer generate reports on its own (see TEST_IMPACT_ANALYSIS_DOC -> How to get testwise coverage)
• [feature] Added test-env option
• [feature] Coverage upload to Azure file storage

v10.1.0

• [feature] Paths passed to the agent can now be relative and contain ant patterns

v10.0.0

• [breaking change] switched to logback for logging. All logging configurations must be replaced with logback XMLs. This fixes Java 10 compatibility issues with Log4j by removing Log4j from the agent
• [feature] make agent log INFO and above to agentdir/logs by default
• [fix] isolate agent further from the application to prevent errors from conflicting library versions

v9.0.3

Minor Fixes and Improvements