QASE
QASE is a tool that help us organize the test cases we create, and it does have a limited (in users), but first we will talk about why to use a test case manager tool
Using a test case manager tool can be incredibly helpful in the field of quality assurance (QA). These type of tools provide to the QA teams centralized platform for managing and organizing test cases, which offers numerous benefits like:
Centralized Test Case Repository: Test case manager tools provide a centralized repository where all test cases can be stored, organized, and accessed by the QA team. This eliminates the need for scattered documents or spreadsheets and ensures that everyone is working with the most up-to-date information.
Improved Test Case Organization: Test case manager tools typically offer features such as folders, tags, and categorization options, allowing test cases to be organized in a structured manner. This makes it easier to locate specific test cases, navigate through different projects, and maintain a systematic approach to testing.
Test Case Traceability: A test case manager tool helps establish traceability between test cases and various requirements or user stories. This allows QA teams to ensure that all requirements are covered by test cases, track the progress of testing, and verify that the software meets the specified criteria.
Reporting and Metrics: Test case manager tools typically offer reporting functionalities that generate metrics, charts, and summaries based on test case execution data. These reports help QA teams analyze test coverage, identify patterns, track progress, and make data-driven decisions for further improvement.
Automation Integration: Many test case manager tools seamlessly integrate with test automation frameworks, allowing automated tests to be managed and executed alongside manual test cases. This integration enhances efficiency, reduces manual effort, and enables the adoption of continuous testing practices.
Talking about QASE
You can check their website: https://qase.io/ Now that we know this, we should check if you are using none, if you are a small organization you can create 5 users, and start creating test cases.
QA Managers / Test Cases writers will have the availability to create test cases and order them in test suites, which will improve the test runs, and control different areas of your testing projects
Once you are logged, you will get a list of the projects you have created, and you will be able to select one, by default, you will have a demo project
Here is a view of the Test Cases Dashboard per project
Will show you the test cases ordered in Test Suites, on each test suite you will have the options to:
- Create a Test Suite (+)
- Edit a test Suite (Pen icon)
- Copy a Test Suite (copy icon)
- Delete a Test Suite (Trash icon)
Test Case Mandatory fields
- Title: refers to the name you will be using
- Status: (Actual, Draft or Deprecated) so you can keep the test cases up to date
- Suite: You will be able to select one of your created test suites
- Severity: as should be known severity refers to the degree of impact a defect or issue has on the functionality, it can be set to: Critical, Mayor, Blocker, Minor or Trivial
- Type: this is related to the type of test that will be require the test case to be ran (usability, regression, performance, accepted, by default will be other)
- Layer: if it is E2E, API, Unit
- Flaky: it means that the test case exhibits inconsistent or unpredictable behavior, you can set it to yes or no
- Milestone: if its related to an specific release
- Behavior: how does it affects the system
- Automation Status: Not automated, to be automated, Automated
- If its manual or automated
- You can add a Description
- Select the environment and Milestone
- You can assign to a resource of your team
- And then you will be able to add Test Cases to it, in a pretty friendly way (as graphic shows, you just need to be clicking the suites, selecting the test cases and add those)
