Github test management made easy!
Github test management integration for QA teams. Push defects from TestCollab to Github in a single click.
Blog
Insights, tutorials, and updates on software testing and QA
Paste images from clipboard, pdf export, ui enhancements and much more…
copy paste images from clipboard, test management software, pdf export test runs
TestRail importer is now available!
Migrate test cases from Testrail to testcolla. Testrail alternative.
How to share test cases across multiple projects to save time and money
Shared test cases among multiple projects. Shared test suites between projects.
Test Case management is now affordable!
Most small teams lack the infrastructure and resources to do testing effectively – and they lack the knowledge and ability to select the right tools for the job.
TestCollab’s public roadmap launched
We have launched our public roadmap and feedback portal.
The all-new TestCollab is here!
Our team worked on almost 2 years to create a whole new TestCollab based on feedback we received over the past 10 years.
DevOps through the vision of a QA
The popular term DevOps is presented as a union of “departments” that has been promoting a set of processes and methods which lead to new thinking about communication and collaboration between them.
Gitlab Test Management now available!
Gitlab test management tool to easily push bugs to Gitlab. Map Gitlab user stories as requirements.
Should you get your testers certified?
Testers certifications has been a thing of debate. There are some points to be considered to settle this: Why you need this? Will this prove to be a paradigm shift for your organization? Are the testers in your team ready for this? Is it going to be a costly affair and is it really worth investing t
Using source code visualizations as a coverage map for testing
I'm not a big fan of tracing or linking dead text requirements documents back to test cases unless it is absolutely required. This got me thinking what else can be used as a reference map for testing....?
When to stop testing or stop documenting?
As product managers, every now and then we have to make decision whether to continue testing that feature or move on? It doesn't just apply to testing efforts, but also to test case coverage & documentation, i.e. to continue writing more test cases for a particular feature or move on to next?
