Continuous Testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate. This practice is strongly associated to the Continuous Delivery approach. In his article “Continuous Testing in .NET”, Damir Arh proposes an overview of continuous testing and how to implement it in Visual Studio.
Software Testing Articles: Load Testing, Unit Testing, Functional Testing
Test management is an essential activity for software testing. The software development teams need to have a central repository to store the test plans, test cases and test results that will provide input for the bug tracking system. In this article, Scott Sherwood presents TestLodge, a test management tool that allows you to manage your test plans, test cases and test runs with ease.
Software testers like software developers might be generally more introverted than extroverted. However, with Agile software development approaches like Scrum, communication between team members and with external stakeholders become a critical for project success. In this extract from her book “Guide to Advanced Software Testing”, Anne Mette Hass presents some general ideas about the communication issues for software testing teams.
The management of test environments is an area mostly neglected in software development projects. In this article, Niall Crawford discusses the basic requirements of test environment management and explains the benefits this activity provides.
The possibilities to write parametrized tests have changed and improved a lot with the release of JUnit 5, the open source unit testing tool for Java. In his blog post “Using JUnit 5 Parameterized Tests, Argument Sources and Converters”, Micha Kops provides an overview covers all new types of parameter sources for JUnit 5 tests as well as the new conversion API for test arguments.
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 the days of DevOps supported by approaches like continuous deployment, the concepts of continuous testing and test automation are essential to support the speed needed for delivering quickly solutions (and hopefully value) to the users. Some of the big questions in the software testing community are “How much should we automate our tests?” and “What tests should we run?”. The technique of Test Impact Analysis helps to answer to this question.