Class FlakyTestAttributes

A container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.

Unique identifier for the attempt to fix this flaky test. Use this ID in the Git commit message in order to trigger the attempt to fix workflow.

When the workflow is triggered the test is automatically retried by the tracer a certain number of configurable times. When all retries pass, the test is automatically marked as fixed in Flaky Test Management. Test runs are tagged with @test.test_management.attempt_to_fix_passed and @test.test_management.is_attempt_to_fix when the attempt to fix workflow is triggered.

The name of the test's code owners as inferred from the repository configuration.

List of environments where this test has been flaky.

The branch name where the test exhibited flakiness for the first time.

The commit SHA where the test exhibited flakiness for the first time.

Unix timestamp when the test exhibited flakiness for the first time.

The category of a flaky test.

The current state of the flaky test.

The branch name where the test exhibited flakiness for the last time.

The commit SHA where the test exhibited flakiness for the last time.

Unix timestamp when the test exhibited flakiness for the last time.

The name of the test module. The definition of module changes slightly per language:

• In .NET, a test module groups every test that is run under the same unit test project.
• In Swift, a test module groups every test that is run for a given bundle.
• In JavaScript, the test modules map one-to-one to test sessions.
• In Java, a test module groups every test that is run by the same Maven Surefire/Failsafe or Gradle Test task execution.
• In Python, a test module groups every test that is run under the same .py file as part of a test suite, which is typically managed by a framework like unittest or pytest.
• In Ruby, a test module groups every test that is run within the same test file, which is typically managed by a framework like RSpec or Minitest.

The test name. A concise name for a test case. Defined in the test itself.

CI pipeline related statistics for the flaky test. This information is only available if test runs are associated with CI pipeline events from CI Visibility.

List of test service names where this test has been flaky.

A test service is a group of tests associated with a project or repository. It contains all the individual tests for your code, optionally organized into test suites, which are like folders for your tests.

The name of the test suite. A group of tests exercising the same unit of code depending on your language and testing framework.

Metadata about the latest failed test run of the flaky test.

Test statistics for the flaky test.