We all know the feeling of how frustrating it is to write a new test case for every application we want to test.

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.

We have launched our public roadmap and feedback portal.

Our team worked on almost 2 years to create a whole new TestCollab based on feedback we received over the past 10 years.

Now, all your failed test cases can be reported to Gitlab in a single click to your Gitlab as bugs so that you can focus your efforts on quality assurance rather than switching between different softwares.

We just recovered our hosted application from an outage. As some of you might have noticed, there was a lag between 'creating a test case' and that test case showing up on test case manage page.

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 time and money?Are these the concerns eating out your mind? Then read on as we analyze the need by answering a few simple questions…

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....?

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?

Today we have released pricing plans for Test Collab. These free forever plans will help development and quality assurance teams to improve their test management without worrying about any payments or subscription ever!