A test suite bundles a few unit test cases and runs them together. In JUnit, both @RunWith and @Suite annotation are used to run the suite test.
Given below is an example that uses TestJunit1& TestJunit2 test classes. For unit testing, I found both Test Driven (tests first, code second) and code first, test second to be extremely useful. Instead of writing code, then writing test. Write code then look at what you THINK the code should be doing. Think about all the intended uses of it and then write a test for each.
Once a bug is found, you can write a unit test for it, you can fix the bug, and the bug can never make it to production again because the unit tests will catch it in the future. Another advantage is that unit tests provide excellent implicit documentation because they show exactly how the code is designed to be used. Test case formats may vary from one organization to another. But using a standard test case format for writing test cases is one step closer Execute the Test Case and Record the results: Test Case can be executed through the tools and results obtained can be easily recorded.
Automate the Defect Tracking: Failed tests are automatically linked to the bug tracker, which in turn can be assigned to the developers and can be tracked by email notifications. You can use this field to reference to other test cases, for example by entering a test case ID here.
Test cases are often grouped in test runs. A test run is simply a collection of test cases that testers should perform in a particular order. JUnit is an open source framework designed by Kent Beck, Erich Gamma for the purpose of writing and running test cases for java programs. In the case of web applications JUnit is used to test the