QASE is a tool that helps Test suites can assist in grouping all of test cases into logical groups. Comprehensive test case features enable to define test case severity and priority, as well as to describe pre-conditions, post-conditions, and steps to reproduce the test case.
So First go to https://app.qase.io/login and login in to the system but if you are a new user just simply Sign up into the system.
After login it redirect into Projects Screen. Top of the Screen here is 4 tabs.
- Project
- Workspace
- Dashboards
- Queries In project here is an option to create new project (Test case). In Workspace here you can add your group members and can view the existing group members list. And for Dashboard and Queries you need Upgrade subscription.
So after that we create a project "Login Module". set Project access type is "Public" so that every one can access that project. but if you select "Private" then you can define the members access on that project.
After we finished create the project it will redirect us in Login Module project screen. So you can create a suit and under the suit you can write test case or can write test case directly.
So here i create a Test suit called "Sign in", set parent shoot as "project root". Mention test description and pre condition (This two is not mandatory), If you test case has pre conditions then you can mention it otherwise skip it.
So create a test case under Sign in suit and mention necessary step under this test case. I am write 4 test cases here two is functional and two of them is non-functional. To fill all the section is very time consuming so i clone the test cases and update necessary field against the test cases.
The most interesting things is it automatic help to convert your Test script in "Gherkin" Script. All the steps in given below
Here i set status is 'Actual, Severity "normal" and Priority "high" ( can set according to test case Severity and Priority). Test type is Functional so set as "Functional" and can set other type dependences on Test case. Set Layer "E2E" can also set E2E (End to end testing) and Api testing. Set milestone according to Sprint value. This a positive Behavior so set it according to test case type. For automation status i will define it as "To be automated" you can select "Not automated or Automation done".
Also mention Pre condition and post condition. Can add related Attachment (Like related UI File) and can also add params (I used this field for API Test case). I add Steps and if you want you can convert it Gherkin or classic.
How to set milestone
And finally save the test case.
After That its time to RUN our test case. This process it manual not automated. User have to select each and every Test case status Passed/Failed/Blocked/Skipped. For each Failed Test case Tester can create Defect report and assign Developer. After that Developer Change the Defect report Status.
Left side of the project you find an Option called "Test Runs". Click on "Test Runs" and it will redirect into Test Run screen. Click on "Start New testcase"
Named your Run title, Add a description (not mandatory). Select Plan , Environment, Tags as i have no plan, Environment, Tags so i can't select any of them. Select Milestone
Top comments (0)