Test management is an essential activity for software testing. The software development teams need to have a central repository to store the test plans, test cases and test results that will provide input for the bug tracking system. In this article, Scott Sherwood presents TestLodge, a test management tool that allows you to manage your test plans, test cases and test runs with ease.
There is a value in writing tests and there is also a cost. The currency is time. The trade-offs are difficult to evaluate in software testing because cost and value are often seen by different people. The writer of the test bears much of the short term cost while long term benefits and cost are borne by the rest of the team.
The management of test environments is an area mostly neglected in software development projects. In this article, Niall Crawford discusses the basic requirements of test environment management and explains the benefits this activity provides.
Learn about the effectiveness of coverage as a technique for evaluating quality of test suite. This presentation shows the utility of coverage by considering its correlation with mutation score, and also shows that coverage is a significant defense against bugs. It also critiques the effectiveness of mutation score as a criteria for test suite quality.
DevOps is currently a trendy approach in software development. The DevOps world mixes the Development and the Operation concepts, but where does software testing find its place in this new approach? This is the topic of the book “Practical Guide to Testing in DevOps” by Katrina Clokie.
The main result of software testing activities is finding bugs that are also called defects or incidents. Besides correcting them, what could you do with the information that they provide? In this extract from her book “Guide to Advanced Software Testing”, Anne Mette Hass discusses how you can define and use metrics from your bug tracking activities to better understand your software testing efforts and software development process.
In software test automation like in programming, the creation phase is always the easier. Then the application is delivered and starts his “maintenance” life, sometimes being tagged with the infamous “legacy” adjective. During this period the code evolve and so should be maintained. This is the same for the code that automate the software testing activity. In his article, Gojko Adzic proposes five ways to reduce the cost of large test suites.