Code coverage is a software testing metric that measures the degree to which the source code of a program is tested by a particular test suite. This metrics is often difficult to understand and interpret for software development teams. In this article, Eran Sher proposes a better approach to code coverage that is more adapted to the current situation of continuous delivery and service architecture.
The status of the testing phase and the role of the software tester are challenged and changing as organizations transition from a classical waterfall methodology to software development towards Agile approaches like Scrum. In his article “Reinventing Testers and Testing to prepare for the Future”, Patrick Prill shares his opinion about this situation and provides some hints for the evolution of software testing and the software tester role.
Session notes that you use when you adopt an exploratory testing approach can be used to capture more than bugs. They not only serve as a memory of a bug, but a structured testing and learning method can be deduced from the session notes.
It is usual that software testers job descriptions will often mainly emphasize the business and technical requirements: experience working in the banking sector, Agile Testing, Selenium, etc. As in many other role however, successful software testing is more about a mindset and soft skills. In this article, Simon Frankish shares some keys attributes that should be considered when hiring a tester.
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.
Software testing can be an isolated activity. While some project activities are done in a team, test execution is typically performed alone. However the concept of pair programming, a well-known practice of eXtremme programming and Agile software development, can also be applied to software testing. This presentation explains how TradeMe pairs testers to remove silos, passively educate, and increase the efficiency of testing.
The DevOps approach has been sometimes considered as a thread for software testers, as it might be a trick to minimize the software testing activities. In this article, Tom Gilmore explains why DevOps should be considered as an opportunity for software quality assurance (QA) as it will support the move towards test automation.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates