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.
Atlassian JIRA is one of the most popular tool for Agile project management. Many add-ons exist for test case management with this tool. In this article, Vladimir Belorusets presents a set of requirements for an efficient test case management process in JIRA that should help you select the best solution for the software testing needs of your organization.
Most of us have had to deal with red builds blocking our testing or have been told to test on flaky environments where half the issues you find would ‘never happen in production’. As a tester, I used to think this wasn’t my problem. What happens though when a thinking tester decides this is her problem and wants to be part of the solution?
One of the famous concept in software testing is the testing pyramid defined by Martin Fowler that is based on strong unit tests and has less user interface (UI) tests at the top. Sometimes organizations have a different view of software tests and the pyramid is not a pyramid anymore. In this blog post, Fabio Pereira discusses the case where the pyramid looks like a cupcake.