Let us start with a small introduction: TestCollab is a modern test cases management tool that offers a complete platform for your application's testing. It supports agile as well as waterfall methodologies, it offers custom user rights management, configurable test plans, custom fields, integration with JIRA and Gitlab, and REST API for custom integrations.
Inspite of gaining popularity amongst IT firms, let us assure you that this product is not limited to the IT industry; due to its flexibility, it can be easily adapted by any industry that has QA needs.
As we go on we will discuss all these features in detail.
Here is a brief introduction of the key terms...
It requires a team effort to achieve organisational goals, testing is not an exception. In TestCollab team members that access the tool are called users each having his/her own profile, rank, and role to perform.
Projects can be understood as the main organisational units of TestCollab. A project can be any software, website, or product that needs testing. Every project would have its own members, test cases, and test plans. Simply a project encapsulates all the objects and functionalities that become the basis for a test case management system.
A test case is
A group, or
A grouping of increments
a software tester writes to demonstrate how an application functions.
These increments or "steps" the tester writes to map out the characteristics of how a software program will behave when it is executed.
It may take many test cases to determine that a software program or system is considered sufficiently scrutinized to be released.
Suites are like folders for your Test Cases. You can group your test cases together in Suites for better management. It's also useful to group test cases in the hierarchy.
Test Plans are groups of test cases that are brought together to achieve specific testing goals. A test plan contains test cases that can be assigned to specific testers for running.
Examples of test plans include regression tests, end-to-end tests, etc.
When it comes to execution of test cases you create a test plan, can have configurations, start and due dates for the test plan and then assign test cases to testers
Test cases may need to be executed more than once depending on their status in a test plan. Runs can hence be created to assign test cases for re-execution that you think need to be tested again.
Configurations lets you create test plans that you can run in different scenarios without creating duplicate test plans!
Ex- You want to create a Test Plan that you want to run in 3 browsers and 3 operating systems. Using configurations, all 9 combinations are generated for you in a single Test Plan.
A defect is reported to the linked defects manager in an event of a test case (or test case step) failure. The tester can take control of the content being pushed at the time of defect reporting including the field values that would be part of the reported defect.
When the test cases are based on a user story/feature request/epic/task added to your project management tool then you can link that issue with test cases as a requirement.