If it helps I'm using on another project: # to find @Ignore tests $ find . -name '*.java' | xargs grep -n1 @Ignore # to find test classes (not methods) $ find . -name '*.java' | xargs grep @Ignore | sed 's#:.*##' | sort -u # to find modules with @Ignore $ find . -name '*.java' | xargs grep @Ignore | sed 's#src/.*##' | sort -u # to count ignored tests $ find . -name '*.java' | xargs grep @Ignore | wc -l
last one mixed with a loop and git allows to follow the evolution and check if it grows or decreases. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> 2018-01-31 22:40 GMT+01:00 Thomas Groh <tg...@google.com>: > Hey everyone; > > I've realized that although we tend to tag any test we suppress (due to > consistent flakiness) in the codebase, and file an associated JIRA issue > with the failure, we don't have any centralized way to track tests that > we're currently suppressing. To try and get more visibility into our > suppressed tests (without running `grep -r @Ignore ...` over the codebase > over and over), I've created a label for these tests, and applied it to all > of the issues that annotated `@Ignore` tests point to. > > Ideally, all of our suppressed tests would be tagged with this label, so > we can get some visibility into which components we would normally expect > to have coverage but don't currently. > > The search to look at all of these issues is > https://issues.apache.org/jira/browse/BEAM-3583?jql= > project%20%3D%20BEAM%20AND%20labels%20%3D%20sickbay > > If you're looking for something to do, or have other issues that should be > labelled, feel free to jump right in. > > Yours, > > Thomas >
