This article discusses how to build a portfolio of scenarios for load testing automation. You have rarely only a single scenario to test, so you have to decide which scenarios to include in your test plans. Criticality, frequency, difficulty and verifiability are the four key factors that should be considered to determine the scenarios to automate.
In this blog post, Roger Hughes explains how SureAssert, an integrated Java unit testing tool for Eclipse, can help solving the problem of having to change your Java unit tests when you change part of your code. You use annotations to define a set of tests for each of your class’s methods instead of writing unit tests. SureAssert automatically checks the annotations, generate and run unit tests.
This just might be the thing that brings a mathematical rigor to Test Driven Development (TDD). If nothing else, it will certainly help programmers choose which tests to write next, and how best to make them pass. Transformations are like refactorings in that they are simple incremental changes to code.
In this blog post James Bach explains the paired exploratory survey technique for software testing. A paired exploratory survey is a process where two testers confront one product at the same time for the purpose of learning a product, preparing for formal testing and/or characterizing its quality as rapidly as possible
Many developers think that testing Java EE applications is hard, inconvenient or too complex. This has not been true since the inception of Java EE 5 more than five years ago. This article explore how to do efficiently unit testing for Java EE applications.
A quick look at using Visual Studio 2010 with NUnit and Silk4NET to create unit tests. We will also be using SilkCentral Test Manager to start from a manual test and automate it with Silk4NET.
This blog post explains how to use Specflow, Moq and Microsoft Unit Testing framework to implement Behavior Driven Development in a .NET context. The author used AAA (Arrange-Act-Assert) and GWT (Given-When-Then) patterns in his code. They are clearly and easily to understand and become standard when you write unit testing and mocking.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates