Acceptance software testing
Robot Framework is a test automation framework for acceptance testing and acceptance test-driven development (ATDD) that uses a keyword-driven testing approach. Thomas Jaspers has created four blog posts that provide a comprehensive tutorial for Robot Framework.
This blog post give a detailed code on how to distribute Robot automated acceptance tests to several virtual box instances using Chef. Pavlo Baron explains how using Vagrant and VirtualBox as a poor’s man virtualization and wiring with Chef, you can run in parallel your acceptance testing suite in a distributed environment.
One of the most common mistakes that teams made was treating specifications or related automation code as less important than production code. Examples of this are giving the automation tasks to less-capable developers and testers and not maintaining the automation layer with the same kind of effort applied to production code. Reference: “Specification by Example – How successful teams deliver the right software”, Gojko Adzic, Manning, 249 pages, IBSN 978-1617290084
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.
Acceptance Testing is defined as the planned evaluation of a system by customers to assess to what degree it satisfies their expectations. The Acceptance Test Engineering Guide provides guidance for technology stakeholders (developers, development leads, testers, test leads, architects, etc.) and business stakeholders (managers, customers, end users, etc) on the discipline of acceptance testing.
This blog post presents a excellent causal loop diagram on acceptance testing automation and then discusses all the factors that make it difficult to automate well acceptance tests.
This article illustrates an approach to automated acceptance testing in developing software with Java. Acceptance tests directly tie into software requirements specification and the key for achieving maintainable tests is proper handling of traceability between the requirements and implementation as well as between the requirements and acceptance tests. An example using Netbeans and Concordion is provided.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates