Test Case Management Tools - Free
Created a test case and executed it in QASE
QASE is a program that assists test suites in arranging all test cases into logical categories. Comprehensive test case capabilities allow you to define the severity and priority of the test case, as well as the pre-conditions, post-conditions, and methods to recreate the test case.
So, first, go to https://app.qase.io/login and sign in to the system, but if you are a new user, simply sign up.
After logging in, you will be redirected to the Projects screen. There are four tabs at the top of the screen.
- Project
- Workspace
- Dashboards
- Queries
There is an option in a project to establish a new project (Test case). In Workspace, you may add new group members and browse the list of existing group members. In addition, an Upgrade membership is required for Dashboard and Queries.
So we did a project called "Demo" and Set the project access type to "Public" so anybody can access it. However, if you pick "Private," you can set the members' access to that project.
When we complete creating the project, we will be sent to the Login Module project panel. So you can design a suit and then write test cases within it, or you can write test cases directly.
So I made a Test suit called "Sign Up" and set the parent shoot to "project root." Indicate the test description and preconditions (optional). If your test case contains preconditions, mention them; otherwise, omit them.
As a result, build a test case under the Sign-Up suite and list the steps required for this test case. I'm writing four test cases here, two of which are functional and two of which are not. Filling up all sections takes a long time, so I clone the test cases and update the relevant fields against the test cases.
The most intriguing feature is its automated assistance in converting your Test script into a "Gherkin" Script. All of the steps are outlined here.
Now, Click on Test Case, & Open This Modal. Where we can make our Test Case.
We've established the test case's title, status, and description here. Additionally, set the following parameters: severity, priority, kind, layer, flakiness, milestone, behaviour, automation status, automation status (both automation status and automation status), and tag for future searches. We have the possibility to add attachments and parameters. Add Test Case Steps lastly (Classic & Gherkin). Finally, save it.
Test runs
It's time to RUN our test case after that. This procedure is not automated; it is manual. Each test case must have a Passed/Failed/Blocked/Skipped status selected by the user. Testers have the ability to assign developers to Defect reports for each failed test case. The developer then changed the status of the defect report.
Added a description and named your run (not mandatory). Because I don't have a plan, an environment, or tags, I should choose Plan, Environment, and Tags. Choose a milestone.
