Tutorials and resources on how to apply test automation in software testing
SpecsFor.Mvc is a software testing tool that enables to create automated acceptance tests using a browser like Internet Explorer or Firefox. This means that your application is tested from the UI all the way down to the database. Unlike other tools which rely on recording actions, you write strongly-typed tests against your ASP.NET MVC controllers, action methods and view models. SpecsFor.Mvc takes care of translating your tests to the browser. Matt Honeycutt blog post provides a detailed introduction to SpecsFor.Mvc. It discusses the challenges of automated acceptance tests and how to install, configure and start using SpecsFor.Mvc with a simple example.
This article discusses how test automation can help achieving continuous delivery. It suggests to start small with a good investment on a robust automation suite, to give it your best people and to cultivate habits in your team that respect tests. Test automation reduces cycle times and also improves the cost of each deployment.This is achieved by earlier feedback to developer through automated tests improves the quality of builds that the testers work on, provided they pick up green builds. There is also a direct reduction in testing cost, as fewer people are needed to run the tests.
The debate about automating or not the software test has always been active in the software development community. This blog post by Ole Laursen discusses the issue of automating software tests with a balanced perspective that presents equally circumstances where automation has benefits or disadvantages.
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.
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.
This video explains the basic differences between different flavors of functional software testing tools. It proposes a selection roadmap and identifies the best vendors for each scenario. It provides pricing info and recommendations on negotiations.
