Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
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.
The increasing adoption of Agile project management frameworks like Scrum and short iteration schedule has a deep impact on the place of software testing and the activity of QA people. In this blog post, Chris Burns tries to answer the often-asked question: “what does QA do on the first day of a Scrum sprint?”
The concept of comparative (or back-to-back) test originates in testing hardware, when the output of the device under test is compared with the output of pre-tested “ideal” device wherein input is provided with the same data. From the viewpoint of Telecom industry, back-to-back test of OSS/BSS (Operating/Business Support Systems) solutions is usually implemented for testing systems managing large amount of data to get maximal coverage of migration and configuration processes. In this article, Yulia Liber discusses pros and cons of implementing comparative tests in Telecom.
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.
Unit testing is a basic software testing activity that should be performed by every software developer. This handout produced by the Computer Science department of Stanford University introduces the ideas of unit testing and provides some examples on how to do it with JUnit in Eclipse.
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.
A recent survey from the Methods & Tools software development magazine shows that the load testing activity is performed only in a minority of software development organizations. The poll asked the question: “Does your organization perform load / performance testing?”
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates