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.
Test-Driven Development (TDD) has been tattered, torn, twisted, stood on its head, and pounded into an pulp of techno-fetishism. TDD was a game-changer, but the focus in the interceding years has shifted from technique to tools and TDD has been devolving into a lost art.
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?”
Successful adoption of unit testing in C++ goes beyond picking a framework: The effectiveness of unit testing is dependent on run-time analysis, static analysis, and other tools to make up the “iron triangle” necessary to get profitable increases in feature velocity and MTBF in the field.
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.
Creating good, effective unit tests in .NET can be harder than it seems. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. First included in Visual Studio 2012, Microsoft Fakes helps you cross this gap.
We all love our tests to speak in the language of business and not in the language of implementation details. In this short presentation I will show how we can get closer to this goal by writing custom assertions with AssertJ.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates