Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
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.
This blog post gives a short tutorial on how to deal with the several issues that prevent the use of functional testing tools (e.g. Fitnesse) with a Silverlight project out of the box. A recent experience with a Silverlight application showed that the approach produces a little overhead, but that this overhead is negligible compared to the benefits of automated functional testing involving the ViewModels.
Mockito is an open source mocking framework for Java. In this series of blog posts, Holger Staudacher shares his experiences with Mockito. He defines “effective” as arriving at clean test and production code as fast as possible. The first post of Effective Mockito explains how to setup Mockito in the Eclipse IDE for the daily work. The second post focuses on Mockito’s @Mock Annotation.
In this blog post, Steve Madsen shares how to use RSpec on an OS/X machine to write unit tests for Objective-C classes. He provides a detailled step by step tutorial on how to install MacRuby, RSpec and how to set up your Cocoa (Mac or iOS) project to perform unit testing with RSpec.
Thucydides is an open source tool that lets you use WebDriver-based unit or Behavior Driven Development (BDD) tests to write more flexible and more reusable WebDriver-based tests, and also to generate documentation about your acceptance tests. In this blog post, John Ferguson Smart explains how you can use Spring dependencies in your acceptance tests with Thucydides if you need to run your acceptance tests against an embedded web server.
One of the biggest challenges facing web applications is the support of web browsers with different versions. This challenge is inherited from the lack of testing the JavaScript code living in the presentation tier from day one. Without unit testing this code, organizations may pay for repeated testing of web applications after upgrading or supporting new browsers. This article shows you how to reduce testing costs using efficient unit testing for JavaScript code.
Integration tests are performed after a successful execution of unit tests. Integration tests are, therefore, executed less frequently, because unit tests will naturally fail often. With this strict separation between unit tests and integration tests, we can save several minutes (sometimes, hours) with each turnaround. This article explains how integration testing can increase your productivity and ensure the deployability of your Java EE 6 application.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates