Software Testing Articles, Blog Posts, Books, Podcasts and Quotes
Unit tests are useful and effective if you remember to make them FIRST. FIRST is an acronym for Fast, Isolated, Repeatable, Self-Verifying and Timely. Each of this points is discussed in the article with examples. The most important thing about unit tests is that they be useful and effective for your programming team. The FIRST mnemonic is a simple mechanism to guide you there.
The FlexMonkium tools provide a consistent Flex application GUI object recognition solution with strong support for the constant Flash plug-in updates. With FlexMonkium, Flex recording and playback is seamlessly interleaved with native Selenium recording and playback. This article provides step-by-step instructions to make Rational Functional Tester works in combination with Selenium and FlexMonkium.
Software testing practitioners, managers and consultants provides in this article illuminating, educational and funny anecdotes about their experiences with test automation. The key points of each story are put in evidence.
This article provides a detailed description on how use Pex and Moles to generate unit tests for a project having external dependency(WCF Proxy) using Visual Studio 2010 SP1. The Pex tool, which automatically generates test suites with high code coverage, will be used to generate unit tests. Moles allows to replace any .NET method with a delegate. They will be generated to isolate the external dependency (WCF proxy) and behavior will be redefined using delegates.
“As we were saying, up-front testing really isn’t testing at all. It is really up-front design through the analysis of our tests. Can we take this testing even further? When XP came out and suggested doing unit tests, many of us realized that if we combined a series of unit tests together, we could get the equivalent of automated acceptance testing.”
In those days where software tests are integrated in continuous integration cycles, it is a necessity that they run in a minimized amount of time. This article explains how through controlled memory usage, increased parallelism, transactional factory invocation, pragmatically judicious test refactoring and a few miscellaneous extras, it was possible to reduce the time needed to run the tests of a ruby on rails application in continuous-integration environments by a factor of ten.
In this blog post, Adrian Smith discusses 7 pitfalls of automating software testing. The seven sins are over indulging on propriety testing tools, too lazy to setup CI server to execute tests, loving the UI so much that all tests are executed through the UI, jealously creating tests and not collaborating, frustration with fragile tests that break intermittently, thinking automated tests will replace all manual testing, too much automated testing not matched to defined system quality.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates