Insights, tutorials, and updates on software testing and QA
A software tester should have a working understanding of the steps needed to “test” a software program functionalities. In software engineering, a software tester uses a structured set of procedures to execute what is known as a “test case”.
Till now it was possible to integrate single user of your issue manager with Test Collab profile.
If you’re using a reusable codebase or share some common libraries across your multiple projects, you know how difficult it can get to manage test cases for such projects.
I’ve been visiting a lot of blogs lately on testing / QC to find out what small businesses in other industries are using for their test management. It seems there is no industry standard tool there ...
ABC Company is a hypothetical profitable small sized software development company with 30 employees... A case study
Today we’ve integrated great design and its comforting my eyes so much. Here are some screenshots ...
Yes, there are a few of them you would want to die for. Here are some examples from our Test Collab application in order of their importance
Your testing process includes creation of new test cases, execution of tests and compiling the stats into important business conclusions. Be it your developer, designer, tester, manager or CEO. In some companies, I’ve observed it is completely left on testers to maintain and execute tests. Don’t be
Not too long ago, we realized that we don't have a very efficient testing procedure in place along with our release cycles. We were infact doing worst at testing when compared to other processes.
A survey conducted few years back concluded that 82% of managers believed that poor software testing was costing them significant amount of money.
