1. Search Bar - This is the part of the tool, which the tester can search for specific test cases. It is also in that field where the search are specified by name of the test case, specific words and responsible for the tests.
2. Test Case Visualization - This field shows all the test cases of the repository, it also displays the results of the searches. Each line represents a test case, with information about: unique identification number of the test, Name of the test case, brief summary about the test case, variability type and priority.
3. Adding Button - The adding button can be selected when the creation of manually test cases is needed. The test case will be saved only if the mandatory fields were filled properly. Warning messages are displayed until the test case obeys the demands.
4. Combo Box - The combo box displays all the extra features of the tool such as the creation of reports, the deletion of one or more selected items, the test case creation, etc.
Test cases will be saved only if the mandatory fields (Test case name, variability type, use case related, steps and priority) were filled properly. Warning messages will be displayed until the test cases obey the demands. The Figure below presents one of these alert messages, requiring the filling of the Name field.
The Figure below presents the details of test suites creation. The test suite will be saved only if the mandatory fields (Name of the Test suite, priority and test cases related) were filled properly. The responsible for the test suite can be associated with the suite and a summary can explain and add information referred to the suite.
The Figure below shows the details of test plans creation. The plan will be saved only if the mandatory fields such as Name of the Test plan, creation date, test suites related and features related were filled properly. The responsible for the test plan can be associated and a summary explains and adds important information related to the test plan. The acceptance criteria field defines how many test cases should pass in order to validate the test plan. Finally, the release field defines the version of the application under test.