-
Notifications
You must be signed in to change notification settings - Fork 11
🧪 Manual Testing
Kira Clark edited this page Mar 21, 2024
·
11 revisions
When manually testing the app, If it's for a ticket or just regression there are a few points to remember.
If you are testing a ticket which has AC's make sure to do those first so that any bugs relating to the ticket can be logged
When it comes to doing regression manual testing on the app the points are:
- Run through the visual aspects of the app making sure the new changes have not changed anything they were not supposed to
- Run through the application using screen readers to make sure that the correct information is read out
- Using keyboard navigation through the pages
- Reset the application and make sure that levels can still be passed with the correct information being sent within the email
- In the sandbox, Run through the defence config toggles and check that the correct pop up appears within the chat window
- Activate defence configs and send a message that would trigger that configuration and check that the response the bot gives to this trigger is expected of the activated configuration
- Modals should be appearing when they are supposed to
- Dialogs are appearing on correct button presses
For each test case the pre-requisite steps are that the app is running and the frontend is open
Description | Steps |
---|---|
Keyboard Navigation |
|
Handbook locked out |
|
Header and Footer |
|
Modal Dialogs |
|
Screen Readers |
|
Level win conditions happy path |
|
Level win conditions unhappy path |
|
Sandbox config |
|
Level 3 config |
|
Email placement |
|
Reset Level |
|
Server off/down |
|
Reset Progress |
|