Tutorials and resources on how to apply test automation in software testing
The increased complexity of browser-executed code has increased the need to write unit test cases for JavaScript code. This article describes some of the most common tools for unit testing JavaScript: QUnit, YUI Test and JSTestDriver. The learning curve can be steep if you do not typically write tests for client-side scripting and testing the user interface could require adjustments in your thought process. This article provides code examples that will walk you through sample test cases.
SpecsFor.Mvc is an open source tools that allows you to create automated acceptance tests using browser automation, meaning your entire application is tested from the UI all the way down to the database, exactly as a real user will use your application. However, unlike many other solutions which rely on recording actions or require you to learn a completely new framework and syntax, SpecsFor.Mvc uses familiar unit-testing tools and syntax.
GHUnit is a test framework for Objective-C, Mac OS X and iPhone 3.x. It can be used standalone or with other testing frameworks like SenTestingKit or GTM. This video shows you how to use it to validate your mobile user interface. GHUnit has the ability to record the look of a UIView so that the developer is aware of any changes since the last test run.
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.
