Software and system testing cost the commercial and defense industry hundreds of millions of dollars annually. In addition, conducting each set of tests takes multiple man-months, delaying time to market of key technologies. In this current economic environment, organizations are looking for ways to reduce the cost of testing and time to market while ensuring that defects are not passed on to the customer.
Behavior-driven development (BDD) is similar to test-driven development (TDD), but the tests for BDD are written in an easier-to-understand language so that developers and clients alike can clearly understand what is being tested. In this article based on chapter 2 of Rails 3 in Action, the authors discuss two tools for BDD: RSpec and Cucumber.
This presentation addresses the missing link in Enterprise Java development: simple, easy integration testing. You will learn how the simplified component model of Java EE can be applied to testable development.
Many developers are not aware of all of the debugging features in Visual Studio, because debugging in Visual Studio “just works.” This article provides an overview of debugging features of Visual Studio that are often ignored by developers like actions in the Breakpoints window or data visualizers. It also discusses external tools and third-party tools you can add to your debugging toolkit.
In this blog post, Dounia Berrada provides an introduction on how to use Selenium WebDriver with Android. Selenium WebDriver is an open source software testing tool that is now available as an extra in the Android SDK. The post explains how to write a basic test with WebDriver to test an Android application.
Dealing with dependencies is the most challenging aspect of test-driven development (TDD). Mocks and stubs are created to isolate the behavior we would like to test. The article “The Art of Mocking” is a good introduction on this topic. Creating all these testing classes by hand can lead to troubles: sometimes developers duplicate these classes and other times the mocks and stubs become more complicated than the code.
Delayed at the end of a project, software testing has often to be done under severe pressure. This article explains how to improve software testing efficiency with risk evaluation. It presents a strategy for prioritizing tests against deadlines and offer solutions for more effective test, which means to find more and more important defects in the same amount of time.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates