Abstract
Specification by Example is a collaborative method for developing software. It involves a workshop where people representing various roles and viewpoints discuss what is to be built, and come up with concrete example scenarios. These scenarios later form the basis for automated (functional) acceptance tests, and are sometimes called ”Living Documentation”, as they are written in a Domain Specific Language and can be read by non-programmers. GUI testing has traditionally used a record-replay paradigm that requires the user interface exists before the tests can be created, and hence have been considered incompatible with a Specification by Example approach. In this experience report we will discuss how we have overcome this apparent contradiction at Jeppesen, and relate an experience using the tool TextTest for GUI testing of Jeppesen’s next-generation Crew Management System.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Adzic, G.: Specification by Example, Bridging the Communcation Gap
Crispin, L., Gregory, J.: Agile Testing
Fowler, M.: Fowler’s bliki, http://martinfowler.com/bliki/PageObject.html
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this paper
Cite this paper
Bache, E., Bache, G. (2014). Specification by Example with GUI Tests - How Could That Work?. In: Cantone, G., Marchesi, M. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2014. Lecture Notes in Business Information Processing, vol 179. Springer, Cham. https://doi.org/10.1007/978-3-319-06862-6_26
Download citation
DOI: https://doi.org/10.1007/978-3-319-06862-6_26
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-06861-9
Online ISBN: 978-3-319-06862-6
eBook Packages: Computer ScienceComputer Science (R0)