Editing JUnit (section)

==JUnit Lifecycle==
Every JUnit test class usually has several test cases. These test cases are subject to the test life cycle. The full JUnit Lifecycle has three major phases:{{sfn|Gulati|Sharma|2017|loc=Chapter §2 JUnit LifeCycle API|pp=37-40}}
# Setup phase - This phase is where the test infrastructure is prepared. Two levels of setup are available. The first type of setup is class-level setup in which a computationally expensive object, such as a database connection, is created and reused, with minimal side effects. Class-level setup is implemented using the {{code|@BeforeAll}} annotation. The other type is setup before running each test case, which uses the {{code|@BeforeEach}} annotation.{{sfn|Gulati|Sharma|2017|loc=Chapter §2 JUnit LifeCycle API|pp=37-40}}
# Test execution - This phase is responsible for running the test and verifying the result. The test result will indicate if the test result is a success or a failure. The {{code|@Test}} annotation is used here.{{sfn|Gulati|Sharma|2017|loc=Chapter §2 JUnit LifeCycle API|pp=37-40}}
# Clean up phase - After all posttest executions are performed, the system may need to perform cleanup. Similar to class-level setup, there is a corresponding class-level clean up. The {{code|@AfterAll}} annotation is used to support class-level clean up. The {{code|@AfterEach}} annotation allows for cleanup after test execution.{{sfn|Gulati|Sharma|2017|loc=Chapter §2 JUnit LifeCycle API|pp=37-40}}