Exclude flaky annoatated tests

Folks seems to be using both androidx.test.filters.FlakyTest as well as
android.platform.test.annotations.FlakyTest to ignore flake tests. While
it's better that there is a more standardized doc for exlcusion, a
strong blocking  test mapping suite should exclude both.

Test: N/A
Bug: 259525599
Change-Id: Ie5cdce3ed3f5c5cea169a36189163ba530c66364
This commit is contained in:
Sam Dubey
2023-01-19 12:33:22 +00:00
parent 4f726c8c39
commit fb754d4d33

View File

@@ -16,6 +16,9 @@
},
{
"exclude-annotation": "android.platform.test.annotations.Postsubmit"
},
{
"exclude-annotation": "android.platform.test.annotations.FlakyTest"
}
]
}
@@ -72,16 +75,16 @@
// Curious where your @Scenario tests will run?
//
// @Ignore: nowhere
// @Staging or @FlakyTest: in staged-postsubmit, but not postsubmit or
// presubmit
// @FlakyTest: in staged-postsubmit, but not blocking postsubmit or
// presubmit
// @Postsubmit: in postsubmit and staged-postsubmit, but not presubmit
// none of the above: in presubmit, postsubmit, and staged-postsubmit
//
// Therefore, please annotate new tests with @Staging, then with @Postsubmit
// once they're ready for postsubmit, then with neither once they're ready
// for presubmit.
// Ideally, please annotate new tests with @FlakyTest, then with @Postsubmit
// once they're ready for postsubmit as they will immediately block go/android-platinum,
// then with neither once they're ready for presubmit.
//
// If you don't use @Staging or @Postsubmit, your new test will immediately
// If you don't use @Postsubmit, your new test will immediately
// block presubmit, which is probably not what you want!
"sysui-platinum-postsubmit": [
{
@@ -98,6 +101,9 @@
},
{
"exclude-annotation": "androidx.test.filters.FlakyTest"
},
{
"exclude-annotation": "android.platform.test.annotations.FlakyTest"
}
]
}
@@ -130,6 +136,9 @@
},
{
"include-filter": "android.platform.test.scenario.sysui"
},
{
"exclude-annotation": "android.platform.test.annotations.FlakyTest"
}
]
}