Qase helps to manage test cases, track their execution status, and report defects. Here is what we need to get started:
- Create a project that will contain all artifacts
- Create a test suite with test cases to store the details of our test
- Create a test run to define which tests should be executed on a product build and track execution status
- Create a defect based on the failed result of a test case
Create a Project
Project is our workspace to keep all parts related to a specific application together. Let’s create a project for an imaginary Food Order mobile application.
To create a project:
1. Open https://app.qase.io/ and log in. As a result, the page “Projects” is shown
Create Test Suite
Test Suite is a big box where we store our test cases organized by sections and subsections. You can create several test suites. For example, Functional and Non-Functional test suites or anything else that should be treated as a separate group of tests.
To create a test suite:
1. On the page “Repository” click on the button “Create new suite”
2. As a result, the page “Create Suite” is shown. Fill in the suite name and optionally other fields. To create a test suite, click on the button “Create suite”
Now, we have the box to add test cases, so let’s create our first test case.
Create Test Case
A test case contains all the details about our test. Only the title is enough to create a checklist-style test case. For a more detailed test case, you can define prerequisites, steps, expected and actual results, etc.
Checklist test case
1. On the page “Test repository”, under “Functional Tests” suite click on the link “+ Create case”
Detailed test case
1. On the page “Test repository”, click on the button “+ Case”
2. As a result, a new page “Create test case” is shown. Let’s fill in the most important fields:
3. Title: describes what is being tested by the test case.
4. Suite: which suite the test case belongs to.
5. Priority: how important is this test case during test execution?
6. Severity: what is the impact on our app’s quality status if this test case fails?
7. Pre-conditions: the prerequisites for our test.
8. Steps to reproduce: list of actions and expected results after each action.
9. To save a test case click on the button “Save”. As a result, the page “Test repository” is shown with a new test case. Icons with arrows in front show the priority and severity of the test case.
We have added our first test cases, let’s execute them in a new test run.
Create Test Run
Test Run represents a set of test cases to be executed on a specific app build along with the status of their execution. We can have 2 versions of the app: iOS and Android. Both need testing, so for each version, we will perform the same test cases in 2 separate Test Runs.
To create a test run:
1. Open page “Test Runs” by clicking on the item “Test Runs” in the left menu
2. Open new test run page by clicking on the button “Start new test run”
Defect report can be created after we fail a test case or one of its steps. It contains test case details (like pre-conditions, steps to reproduce, etc.) and describes an actual result. We can also add attachments if necessary.
To create a defect:
1. In a test run, set status Failed for a test case or its step by clicking on the button “failed” in the test case. As a result, a popup window “Failed” is shown. By default, field “Defect title” contains test case title
2. Let’s describe the actual result and add attachment by clicking on the area “Drop files here to upload” and specifying a file to upload. After this we can create new defect by clicking on the button “Save result”
3. As a result, the test case will get Failed status and a new defect will appear in the section “Defects”. You can open this section by clicking on the “Defects” on the left side menu. Defect got the same Severity as it was set in the test case.
4. We can open the report by clicking on the Defect title “Find restaurant by name”. There are a number of fields from the test case (pre-conditions, steps to reproduce, severity and priority) added automatically, while we just needed to provide Actual result and Attachments
This was the most important Qase functionality to start using it. There are many more things to explore: test plans, shared steps, custom fields, sharing cases with team members, integrations with systems like Jira, Slack, GitHub etc., and much more. Stay tuned!