Code coverage is a metric that gives the degree to which the source code of a program is tested by a particular test suite. This metric is provided by open source or commercial code coverage tools and displayed in quality dashboards like SonarQube. There are many discussions about the right level of code coverage. In his book Quality Code, Stephen Vance explains the limit of this metric.
As software development companies grow, it becomes more important to have a formal quality assurance (QA) process. In this article, Veronika Olshevskaya discusses six mistakes that you might do when you set up your QA department and suggests solutions to avoid making them.
In theory everyone on an Agile team is responsible for software testing, but in practice this is rarely the case. Learn how to make quality a team sport in Scrum teams.
Software testing is an activity that is not always well considered in the software development community. When companies use a “silo” organization, the relationships between developers and testers are often tense. Developers complain that testers are not understanding the system and testers complain that developers write poor quality code. In this blog post, Emma Armstrong give some hints to help the software tester engineer to portray his role in a positive way.
Certification is a process that has gradually spread amongst all areas of software development. Software testing certifications are mainly managed by the International Software Testing Qualifications Board (ISTQB) and its local affiliates. The Professional Tester’s Manifesto is a strong statement about the certification process in software testing.
What is a professional software tester? In this blog post, Huib Schoots explains that he cannot understand why testers who call themselves professionals know so little about software testing and do not study it. He tries to answer this question and explain the difference between professional testers and testers by profession.
Software testing during the transition to Agile is not easy. This third part explains how your software quality assurance processes should change. It discusses how to cope with rapid development cycle and frequent code changes that are at the heart of the Agile approaches.