java-unit-testing

AIR principles for Java unit testing require tests to be Automatic, Independent, and Repeatable. This foundation ensures tests run without manual intervention, do not interfere with each other, and produce consistent results across executions.

To ensure isolation and non-interference, place Java unit tests under the src/test/java directory. Design tests using BCDE-based methodology with minimal external dependencies and implement data isolation techniques like optional rollback for database interactions.

The recommended code coverage target for Java unit tests is 70% statement coverage overall. For core modules within the Java project, the target increases to 100% coverage to catch regressions early and improve reliability.

Yes, you can run automated Java unit tests in a CI workflow. The standards apply during code development and CI workflows to guide test design, verify AIR-based testing practices, and enforce coverage goals across core modules.

Database tests in Java unit testing should be handled using data isolation and optional rollback. This approach maintains the Independent and Repeatable AIR principles by ensuring database modifications do not affect subsequent test executions.