0.6.0

New Features

• Automatically symbolicate crashes when running macOS tests or iOS tests on simulator.
• Network payload size is configurable by environment variable (DD_MAX_PAYLOAD_SIZE). Is now also bigger by default, 1024 bytes.

Bug Fixes

• Fixes a thread race condition that could show in Thread Sanitizer (in opentelemetry)

Improvements

• CI environment variables are tested automatically now against the spec
• Uses opentelemetry-swift version 0.5.0

0.5.1

New Features

• Add commit information to tests when using Bitrise CI (needs adding environment variables in Xcode)

Bug Fixes

• Fixes Wall Time calculation for Bitrise when tests are run several times for the same commit

Improvements

• Updated environment variables for CI's

0.5.0

New Features

• Capture automatically dd-sdk-ios traces and logs as part of the tests (a new version of dd-sdk-ios is needed)
• Framework can now be used using semantic versioning in SPM, since all dependencies are also using semantic versioning.

Bug Fixes

• Some tags were dissapearing randomly in benchmark tests ( test name, test suite, ...)
• Branch environment variable in Bitbucket was not correctly set.

Improvements

• Framework is now tested and released automatically on Bitrise CI using make tests and make release
• It links with opentelemetry-swift v0.4.0

0.4.0

New Features

• Network spans of requests that were started during a test and didn't finish are now reported. They are marked with the tag unfinished
• New makefile to build a XCFramework that supports all platforms, and can be used to link with the project in binary form. The result is attached as a zip file to the release

Bug Fixes

• Fixes a potential crash in network instrumentation
• Removed stderr synchronization at end of tests, in some environments that captured stderr themselves made each test run 1 second slower

Improvements

• Network instrumentation is less intrusive when injecting headers is disabled
• Improvements on CI information for Bitrise (there are changes in environment variables)
• Added new tags indicating the platform and device where tests are run

0.3.1

Bug Fixes

• Fixes a potential crash in network instrumentation
• Network instrumentation is less intrusive when injecting headers is disabled

0.3.0

New Features

• Added support for UITests, framework must be linked in both the test target and the application being tested. Configuration only needed in test action. It also supports reporting crashes in the app under tests.
• Added new network auto-instrumentation, now auto instruments much more methods and network libraries.
• Network auto instrumentation reports standard non-private request and response headers by default, redacting the rest. It can be configured to also log extra headers.
• Network auto instrumentation can be configured to report also the first 512 bytes of request and response payloads, it is disabled by default. It can be enabled both by environment variable or in code using DDInstrumentationControl methods

Bug Fixes

• Benchmark tests now reports under the metrics group in the Span, so values are now numeric.
• Disabling Stdout capturing doesn't add one second extra time to each test.

Improvements

• Replaced test.traits tag with test.bundle, which will show as a facet in a future release.
• Added git.commit.sha tag that will replace git.commit_sha in the near future

0.2.0

New Features

• Added support for crashes in tests. It captures and reports the crash information along with the call stack
• Added support for stdout and stderr capturing. It logs all output sent to these streams as logs associated with the span. It allows recovering print(), NSLog(), os_log(), UI Test steps, ...
• Added support for enabling and disabling instrumentation using environment variables or code

Bug Fixes

• Fixed support for XCTApplicationLaunchMetric benchmark

Improvements

• Improved error information in spans
• Benchmark tests now include much more information

0.1.0

This is the first release of the testing instrumentation library for Swift and Objective-C.

Features

• It reports test status and duration for each test (pass, fail, skipped)
• Supports benchmarking tests reporting mean duration
• Instruments network calls related to each test
• Injects Datadog and OpenTelemetry headers for following the traces

There are some getting started instruction in the README file, but still quite incomplete