Introduction
Welcome
The purpose of this website is to get you fully acquainted with QualityWatcher, which should be used as a replacement for our Agile Test Case Template. After reviewing this page, you should be able to use this tool without any assistance.
QualityWatcher Legendβ
Term | Definition |
---|---|
app.qualitywatcher.com | Direct URL for the QualityWatcher app. |
qualitywatcher.com | Landing page for QualityWatcher. You cannot access the app from this website; you have to use the direct URL for the app. |
Workspace | A QualityWatcher Workspace is where you can find all information for an organization. |
Project | A collection of test suites related to a specific application or software. |
Test Suite Templates | A collection of predefined test cases that can be used to test specific behavior of a software or application. |
Test Suite | A collection of test cases to be used to test specific behavior of a software or application. |
Test Case | A test case is a singular set of steps or instructions for a tester to perform that validates a specific aspect of a product or application functionality. |
Test Run | A specific set of test cases being executed. |
Test Run Plan | A test run plan is a grouping of test runs. We use test run configurations to create test run plans. |
Test Run Configuration | Test run configurations are a grouping mechanism for supporting cross-browser/cross-platform testing within a test run. |
Environment | An environment is an entity that can be used to describe where a test was conducted. |
API Key | An application programming interface (API) key is a code used to identify and authenticate an application or user. |
QualityWatcher User Typesβ
- Owner
- Admin
- Editor
- Viewer
Access Control Matrixβ
Actions | Owner | Admin | Viewer | Editor |
---|---|---|---|---|
ADMIN | ||||
Invite Users | β | β | ||
Assign Admin Role | β | β | ||
Assign Viewer Role | β | β | ||
Assign Editor Role | β | β | ||
WORKSPACE | ||||
Update Workspace Metadata | β | β | ||
Remove Users from Workspace | β | β | ||
View Workspace Members | β | β | ||
TEST CASE | ||||
Create a Test Case | β | β | β | |
View a Test Case | β | β | β | β |
Update a Test Case | β | β | β | |
Delete a Test Case | β | β | β | |
TEST SUITE | ||||
Create a Test Suite | β | β | β | |
View a Test Suite | β | β | β | β |
Update a Test Suite | β | β | β | |
Delete a Test Suite | β | β | β | |
Import a Test Suite | β | β | β | |
TEST RUN | ||||
Create a Test Run | β | β | β | |
View a Test Run and Test Summary | β | β | β | β |
Update a Test Run | β | β | β | |
Delete a Test Run | β | β | β | |
Complete a Test Run | β | β | β | |
TEST RUN PLAN | ||||
Create a Test Run Plan | β | β | β | |
View a Test Run Plan Summary | β | β | β | β |
Update a Test Run Plan | β | β | β | |
Delete a Test Run Plan | β | β | β | |
Complete a Test Run Plan | β | β | β | |
PROJECT | ||||
Create a Project | β | β | ||
View a Project | β | β | β | β |
Update a Project | β | β | ||
REPORT | ||||
Create a Report | β | β | β | |
View a Report | β | β | β | |
Update a Report | β | β | ||
JIRA INTEGRATION | ||||
Integrate Jira | β | β | ||
Create bug tickets | β | β | ||
Disconnect from Jira | β | β | ||
API KEY | ||||
Create API key | β | β | ||
View API key | β | β | ||
SUBSCRIPTION | ||||
Manage Subscription | β | |||
TEST RUN CONFIGURATION | ||||
Create a Test Run Configuration | β | β | β | |
View a Test Run Configuration | β | β | β | |
Update a Test Run Configuration | β | β | β | |
Delete a Test Run Configuration | β | β | β | |
ENVIRONMENT | ||||
Create an Environment | β | β | β | |
View an Environment | β | β | β | |
Update an Environment | β | β | β | |
Delete an Environment | β | β | β |
Where to Create Test Casesβ
Yes, you guessed it! QualityWatcher - Test case management tool!!
To get started, you need to create a QualityWatcher Workspace, which is essentially setting up a QualityWatcher account for an organization.
Use the link belowππΎ or go to the direct URL for the QualityWatcher app.
Create a QualityWatcher Workspace - (QualityWatcher )
info
You can only use the same email once even if itβs a different workspace. If you are working with multiple workspaces in the same organization, then we recommend using a wildcard on your email.
[name]+[project|workspace]@[domain] - jdoe+newproject@test.com
Registration Screen |