-
Notifications
You must be signed in to change notification settings - Fork 0
Testing
| Name | File | Document id |
|---|---|---|
| Testing | Testing.pdf | 15.0 |
By testing the code the developers uncover flaws of the application. Additionally it is also a way to demonstrate quality of the code. The tests is then a form of documentation that shows that the system works, and meets the requirements set by the client.
We have used JUnit testing, which is a unit testing framework for Java. A unit test tests a concrete functionality, class or component of the system, and is created by developers while the program is under development. A JUnit test usually follows the pattern of Arrange-Act-Assert. First, you arrange the test data, then you run the methods and finally assert the result. The result can be asserted for both behavior and condition of the tests. You want the tests to be precise and exact. Which means that you want expected and consistent results.
Tests for the MainRegister, the tests are divided into two nested classes, Category and MainTask. Category includes tests for all methods connected to the Category class, and MainTask includes tests for all methods connected to the MainTask class. All tested methods have positive and negative tests.

Tests for the application’s persistence. The tests both read and write functionality. All methods tested have positive and negative tests.
