Our 'Testing Documentation' articles
A test plan in software testing helps guide the testing team throughout the project. A test plan is really the blueprint of the testing process.
Setting up a simple but well ordered QA toolbox for your team is a practical way to keep tools and documents together in one place and within easy reach.
Can a test summary report help freelancers to get work? Yes. Learn how to impress future clients by showing how well you can write a test summary report.
What is Test Strategy in Software Testing? It’s an important part of the testing lifecycle and we look what should be included in a test strategy document.
Requirements are fundamental to the success of software projects. Writing better requirements helps ensure your team is successful.
There are various styles of test cases in software testing; positive test cases, negative test cases and destructive test cases. Each are equally important.
There are many different types of test cases in software testing. Each type of test case helps us target software testing in a different way.
There are many terms in the software testing world. Some of them sound the same and share similar functions. So, what is a test case in software testing?
Knowledge transfer plays a big role in software development. A support handover document can help keep your support team in the loop on what's been changed.
A test case is a set of steps and preconditions which a tester uses to execute a software test. Here are tips on how to write test cases for software.