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.
In this blog post Sebastians Lutzky start a series of posts that will explain the concept of unit testing in the context of design by contract.
In this blog post, David Tobey shares with us how he used the open source load testing tool JMeter for functional testing. JMeter allows him to automate part of the functional testing process, making it more reliable and less time-consuming.
Story Driven Development (SDD) helps close the gap between the language of developers and product owners so they can clearly define when software is “done”. Readable and executable product requirements are now possible. We’ll explore tips for integrating SDD into your existing workflow and cover technical details for implementing and maintaining stories using cutting-edge tools and libraries.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates