In this lesson, we are going to look into a meta-annotation used for grouping tests together,
@Tag. It's the successor to JUnit 4's
Category, and allows developers to tag tests with
String identifiers, then later drive the execution of their test suite based on these tags. We'll explore how the Gradle build system can include or exclude specific tests in both Java and Android environments.
- Similar tests may be tagged with the same ID (think "end-to-end tests" vs. "UI tests")
- Marking slow-running tests may improve your daily workflow for running tests
- Gradle provides a DSL to include and exclude tags
- Android can specify different include/exclude statements per variant