This documentation is targeted towards the persons interested in learning how to use Test Collab.
Test Collab is a modern test management tool that offers a complete platform for your application's testing. It integrates with all popular bug trackers and test automation tools. It also supports agile methodology, requirements management, test plans and scheduling.
This product is not limited to IT industry, due to its flexibility it can be easily adapted by any industry that has QA needs.
Throughout your reading, we will try to familiarize you with the application concepts.
With Test Collab one can create projects, manage project's requirements, set milestones, define test suites, test cases, create test plans, assign test executions, get them running, and analyze the results.
Test Collab also supports two way integration with issue tracking systems like JIRA and Redmine. It can also be integrated with any test automation tool.
As we go on we will discuss all these features in detail.
Starting with definitions of key terms, one by one.
Projects are main organizational units of Test Collab. A project can be any software, website or a product. Every project has its own members, test suites, test cases, requirements, test plans and test executions.
Apart from administrative tasks, anything you will do in this application will be under a project. Simply stated project encapsulates all the objects and functionalities that become the basis for test case management system.
Project requirements , project specifications , project objectives or simply requirements form the basis of a product. Analysts, developers, testers all depend on these requirements as they state what features the product should have and how they should be implemented.
Milestones mark key points in a project so you can have a bird-eye view over things that need to be done, when and who is responsible. Milestone can be a single day event or a time period with start and due dates.
Set the milestone, as it will help team members in knowing what the goals are, who is responsible and what the deadlines are.
A test suite is a collection of test cases that are intended to be used to test a process or software program to show that it has some specified set of behaviors.
A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing.
A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests.
A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not.
It may take many test cases to determine that a software program or system is considered sufficiently scrutinized to be released.
Test cases are often referred to as test scripts, particularly when written. Written test cases are usually collected into test suites.
A test case is
- A single,
- 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.
The core entity around which the all processes and sub processes are designed is a test case.
A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements.
Test Execution is an entity which groups together the test cases and their testers. They can be easily assigned and monitored.
Here testers are team members of a project, or remote executers defined under the application.