Checklist is a list of tasks used to systematize the testing process. Each item in a checklist is a check that needs to be performed.
A checklist can cover different testing criteria:
- functionality
- reliability
- performance
- security
Checklist
How to create a checklist
Checklist items are based on the requirements. The checklist format may vary, but it should include:
Title:
a clear title that quickly conveys what is being checked
Description:
a brief description of the check, which may include the necessary steps and test conditions
Result:
the expected outcome of the check
Example of a completed checklist
| Title | Description | Result | Status |
|---|---|---|---|
| Login to the system | Login with a valid username and password | The user should successfully log in to the system |
|
| Login to the system | Login with an invalid username and/or password | The user must not be authenticated in the system |
|
After you perform the scenario, you fill in the check status.
Status:
the actual result of the test execution
Passed
The behaviour matches the expected result.
Failed
A bug was found: the behaviour differs from the expected result.
Blocked
The check cannot be performed due to external reasons (for example, the service is unavailable).
Skipped
The check is intentionally skipped, for example, it is not part of the current release.
Rules for a good checklist
Base your checklist on the requirements when creating checklist items
Split the check into several simpler ones if it becomes too complex
Separate checklists for different pieces of functionality
Keep the checklist up to date
Task
Test the «Login» form. Use the test user credentials that have already been registered.
Test user data:
| Name | tester-today |
| Email address | tester.today.help@gmail.com |
| Password | password |
Run the checks according to the checklist created from the requirements.
Login
Task available to premium users!
Уровень повышен!
