Optional additionalA container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.
Optional attemptUnique 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.
Optional codeownersThe name of the test's code owners as inferred from the repository configuration.
Optional envsList of environments where this test has been flaky.
Optional firstThe branch name where the test exhibited flakiness for the first time.
Optional firstThe commit SHA where the test exhibited flakiness for the first time.
Optional firstUnix timestamp when the test exhibited flakiness for the first time.
Optional flakyThe category of a flaky test.
Optional flakyThe current state of the flaky test.
Optional lastThe branch name where the test exhibited flakiness for the last time.
Optional lastThe commit SHA where the test exhibited flakiness for the last time.
Optional lastUnix timestamp when the test exhibited flakiness for the last time.
Optional moduleThe name of the test module. The definition of module changes slightly per language:
.py file as part of a test suite, which is typically managed by a framework like unittest or pytest.RSpec or Minitest.Optional nameThe test name. A concise name for a test case. Defined in the test itself.
Optional pipelineCI pipeline related statistics for the flaky test. This information is only available if test runs are associated with CI pipeline events from CI Visibility.
Optional servicesList 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.
Optional suiteThe name of the test suite. A group of tests exercising the same unit of code depending on your language and testing framework.
Optional testMetadata about the latest failed test run of the flaky test.
Optional testTest statistics for the flaky test.
Generated using TypeDoc
Attributes of a flaky test.