Software Testing Articles: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
Test Driven Development (TDD) is a powerful tool to produce quality code, but if it is not used correctly it can also put your project in a difficult position if it is not used correctly. In this article, Jakub Nabrdalik explains that TDD is simple to learn, but hard to master. He shares some tips on how to avoid Test Driven Development traps.
This article from Keith Burnell presents best practices and techniques to increase the testability of ASP.NET MVC applications. This includes how to structure the solution, architecting the code to handle the injection of dependencies and implementing dependency injection with StructureMap.
This article explains how you can set up a unit test method that will retrieve values used in the test method from a data source using the Microsoft unit test framework for managed code. Creating these data-driven unit tests makes it easy to test a multiple inputs with a single method.
Many organizations are adopting Agile development practices and the Scrum framework for project management. With a software testing perspective, one of the main challenges of this approach is to complete all software testing activities during iterations that could last only one to two weeks. In this article, Clemens Reijnen provides five tips for getting software testing done in a Scrum sprint.
This article by Benjamin Day recommends to use custom counters when you perform load testing. It discusses how Visual Studio 2012 load-testing features call help you solve performance problems. The article describes how to set up Visual Studio to perform load testing, particularly the ability to capture Windows Performance Monitor Counters (PerfMon Counters).
This extract from the book “Pragmatic Unit Testing in Java with JUnit” written by Andy Hunt and Dave Thomas provides an introduction to the usage of mock objects during Java unit tests. They define the usage of mocks in unit testing as the unit similar to the use of lighting doubles in the movies: A mock object is simply a debug replacement for a real-world object.
Best practices for unit testing are that you should only write for each test a single assertion. In this article intends, Jonathan Allen tries to demonstrate that unit tests with multiple assertions are both necessary and beneficial.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates