⌨️
CS A-Level NEA Documentation
  • Introduction
  • 1. Background and Identification of the Problem
  • 2. Interview With the Client
  • 3. Chosen Solution
  • 4. Concept Flowcharts
  • 5. Documented Design
    • 5.1. Identifying Suitable Algorithms
    • 5.2. Designing the Database
    • 5.3. Identifying Suitable Validation
    • 5.4. Designing the Graphical User Interface (GUI)
    • 5.5. Test Plan
  • 6. Technical Solution
    • Implementing the Desktop Application
    • Implementing the Mobile Application
  • 7. Testing
    • Evidence of Testing
  • 8. Evaluation
Powered by GitBook
On this page
  • Test 1:
  • Test 2:
  • Test 3:
  • Test 4:
  • Test 5:
  • Test 6:
  • Test 7:
  • Test 8:
  • Test 9:
  • Test 10:
  • Test 11:
  • Test 12:
  • Test 13:
  • Test 14:
  • Test 15:
  • Test 16:
  • Test 17:
  • Test 18:
  • Test 19:
  • Test 20:
  • Test 21:
  • Test 22:
  • Test 23:
  • Test 24:
  • Test 25:
  • Test 26:
  • Test 27:
  • Test 28:
  • Test 29:
  • Test 30:
  • Test 31:
  • Test 32:
  • Test 33:
  • Test 34:
  • Test 35:
  1. 7. Testing

Evidence of Testing

Previous7. TestingNext8. Evaluation

Last updated 2 years ago

Test 1:

Checking that a connection to the database can be established with the correct database URL and Password:

Test 2:

Checking that the appropriate error message is displayed if the connection to the database cannot be established.

Test 3:

Checking that a valid username and password combination is accepted when signing in.

Test 4:

Checking that an invalid username and password combination is rejected when signing in.

Test 5:

Checking that if the correct user credentials do not match to an administrator or secretary account, access to the Administrator Form is denied.te

Test 6:

Checking that the combination of correct credentials, along with the user type administrator or secretary hides the Log In form and displays the Administrator form.

Test 7:

Checking that an appropriate Absent Student list is generated and displayed without choosing a group.

Test 8:

Checking that an appropriate Absent Student list is generated and displayed given a selected group.

Test 9:

Checking that a .csv file is generated successfully at the selected file path.

Test 10:

Checking that a group selected results in the right list of students presented.

Test 11:

Checking that an error message is displayed when no group is selected to show its member students.

Test 12:

Check that an error message is displayed when no student is selected to be removed.

Test 13:

Check that an incorrectly structured .csv file has been selected.

Test 14:

Checking that a semester’s initial date is not later than the final date selected by the user.

Test 15:

Checking that all dates are added to the database in the “Semesters” and “Dates” tables.

Test 16:

Checking that an error message is displayed when no semester is selected to be removed.

Test 17:

Checking for appropriate error message when no group name was used to add a new group.

Test 18:

Checking that a group is added when an appropriate name has been entered.

Test 19:

Checking that an error message is displayed when no group is selected to be removed.

Test 20:

Checking that a single group and all its member students are deleted successfully.

Test 21:

Checking that two correctly structured .csv files have been selected.

Contents of test-part1.csv:

2,0,0,0,2
0,2,0,2,0
0,2,2,0,2
0,0,2,2,0
2,5,3,8,12
5,0,0,8,12
3,0,0,0,0

Contents of test-part2.csv:

E2,NULL,NULL,NULL,E2
NULL,E2,NULL,E2,NULL
NULL,E2,E2,NULL,E2
NULL,NULL,E2,E2,NULL
E2,D1,D1,E2,E2
E2,NULL,NULL,E2,E2
D1,NULL,NULL,NULL,NULL

Test 22:

Checking that a single user has been selected when uploading their schedule.

Test 23:

Checking that a single user has been selected when changing their password.

Test 24:

Checking that an empty password was not provided when changing password for a user.

Test 25:

Inserting the same password twice changes the current password of the user to the new one.

Looking up the user in the users table shows the updated password:

Test 26:

Inserting different passwords when changing the selected user’s password results in an error message.

Test 27:

Checking that a single user has been selected when deleting them from the database.

Test 28:

Selecting “Yes” in the popup window deletes the selected user from the database.

Test 29:

Selecting “No” in the popup window does not delete the user from the database.

Test 30:

Checking that a single lesson has been selected when removing it from the database.

Test 31:

Checking that a numeric ID results to creating a new lesson in the database.

Test 32:

Checking that a lesson is not created when a non-numeric lesson ID is provided.

Test 33:

Checking that a non-empty post text has been provided.

Test 34:

Checking that the current password and new passwords result in the password being changed.

Test 35:

Checking that the feed posts are fetched on launch.

The lesson is added to the database and the list of lessons is fetched once again.