This presentation introduces the audience to BDD - the Behavior-Driven Development method and how it can be applied to development and testing of GUI applications. We will also try to debunk myths and false hopes surrounding it. BDD centers around stories written in an "ubiquitous language" that describe the expected behavior of an application. The use of a human-readable language allows for technical as well as non-technical project stakeholders to participate in authoring of feature descriptions. Those descriptions then serve as a base for the work of both developers and testers. Classic agile and test-driven programming takes an inside-out approach by focussing on the specification and testing of the API of individual software components. BDD, on the other hand, looks at the application as a whole and puts interaction sequences and their expected outcomes into the foreground. An introduction to the de-facto standard BDD language Gherkin will be given. It became popular as part of the Cucumber Ruby testing framework but has found its way into various free and commercial tools that will be listed. A sample feature file including scenarios, outlines and backgrounds descriptions will be developed live using the Squish GUI Tester. This feature file can already be "run" in dry mode. We'll see different types of usage of this input: * A mean to communicate with the customer. * Documentation for the acceptance test before delivery * A sequence to walk through for manual testing * Automated GUI testing through tools like Squish.

1. Behavior Driven GUI Testing
STUGHH 2015
by Reginald Stadlbauer

2. About me
 Name: Reginald Stadlbauer
 Company: froglogic GmbH
 Position: co-founder and CEO
 Worked as Software Engineer at Trolltech and the KDE project

3. About froglogic
 HQ: Hamburg
 Founded: 2003
 US presence since 2008
 Product focus on Squish
- Squish GUI Tester (Cross-Platform/Cross-Technology GUI Test Automation)
- Squish Coco (C, C++ and C# Code Coverage)
 More than 3.000 customers world-wide

4. Overview
 What is BDD and TDD
 Automating a Behavior Driven Test
 Live Demo & Conclusion

5. What is BDD / BDT?
“BDD is a second-generation, outside-in, pull-based, multiple-stakeholder, multiple-scale,
high-automation, agile methodology. It describes a cycle of interactions with well-defined
outputs, resulting in the delivery of working, tested software that matters.” - Dan North
http://en.wikipedia.org/wiki/Behavior-driven_development
OR...

6. What is BDD / BDT?
 Based on Test Driven Development
- Write (failing) test
- Implement feature until test passes
- Unit-Test level granularity (inside-out)
 But
- Focus on application's behavior and specification
- Description in a human-readable DSL (e.g. Gherkin)
- Less focus on implementation details

7. Versatile usage of Feature Files
 User story / feature specification
 Communicate with customer / users
 Documentation of acceptance test
 Sequence to walk through for manual tests
 Storyboard for automation of tests

8. Why BDD/BDT
 “Test first” development on a higher level
 Clearly separate test logic from implementation
 Allow non-programmers to define features & tests
 Have a common, single language two communicate

9. What is BDD / BDT – Unit Conversion

10. What is BDD / BDT – Unit Conversion
Feature: Valid conversion
Scenario: Convert meter in centimeter
Given the Unit Converter is running
When I enter 378.9
And choose to convert from "m"
And choose to convert to "cm"
And click Convert
Then 37890 should be displayed in the result field
Feature
File
(Gherkin)

11. What is BDD / BDT – Unit Conversion
Feature: Invalid conversion
Scenario: Mix units
Given the Unit Converter is running
When I enter 378.9
And choose to convert from "m"
And choose to convert to "kg"
And click Convert
Then ERROR should be displayed in the result field
And "Unit type mismatch: Length vs. Weight." should be displayed in red
Feature
File
(Gherkin)

12. What is BDD / BDT – The Process
Write a failing
Feature Test
Make
Feature Test
pass
Implement/
Refactor
Code
Test
Manually Automated

13. Automating a Behavior Driven GUI Test
 Requirements
- BDT framework
- Test Automation framework (GUI test tool, ...)
- Glue between both

14. BDT Framework – Generate Skeletons
 Parse feature files
 Generate step definition skeletons (functions and annotations) in
preferred language
Test.feature
Feature: Valid conversion
Scenario: Convert meter in centimeter
Given the Unit Converter is running
When I enter 378.9
....
Test.py
@Step("Given the Unit Converter is running")
def step(context):
test.warning("Implement me”)
@Step("When I enter 378.9")
def step(context):
test.warning("Implement me”)

15. BDT Framework – Run Feature Files
 Parse feature files
 Execute feature files by mapping to steps to step definitions (functions)
 Reporting
Test.feature
Feature: Valid conversion
Scenario: Convert meter in centimeter
Given the Unit Converter is running
When I enter 378.9
....
Test.py
@Step("Given the Unit Converter is running")
def step(context):
[...]
@Step("When I enter 378.9")
def step(context):
[...]

16. Test Automation framework
 Support the specific UI technology of Application
 Support the scripting/programming language of the BDT framework
 Tooling for convenient test creation, maintenance and debugging
Test.py
@Step("Given the Unit Converter is running")
def step(context):
startApplication("UnitConverter”)
@Step("When I enter 378.9")
def step(context):
click("FromField”)
typeText("378.9”)

17. Integrating BDT and Test Automation
frameworks
 Need to “talk the same language”
 Reporting
 Debugging

18. BDT Frameworks
 Cucumber
 JBehave
 Behave
 SpecFlow
 RSpec
 Lettuce
 Squish GUI Tester
 ...

19. Test Automation frameworks
 CppUnit
 GoogleTest
 xUnit
 NUnit
 JUnit
 Squish GUI Tester
 HP QTP
 Rational Functional Tester
 Selenium
 ...

20. Live Demos
 BDD GUI test for cross-platform Unit Converter
- Valid conversion
- Invalid conversion
- Passing parameters
- Scenario Outline

21. Q & A
Contact me reggie@froglogic.com
Free and supported trial of Squish at http://www.froglogic.com/evaluate

22. About Squish GUI Tester
 Cross-Platform / Cross-GUI-Technology Test Automation
- Windows, Linux, Mac OS X, Unix, Embedded OSes, RTOSes, Mobile
- Java (Swing/AWT, SWT/RCP, JavaFx), Qt/QML/QtQuick, Web, MFC,
WinForms, WPF, iOS, Cocoa, Carbon, Android, Tk, Flex, …
 Object-based GUI object identification
 Record & replay
 Powerful scripting (JavaScript, Python, Ruby, Tcl, Perl)
 Eclipse-based IDE
 Built-in BDD framework and support
 Batch-testing via command-line tools
 Remote/distributed testing architecture
 Integrations: Microsoft ALM, HP QC/ALM, Rational RQM, Seapine TCM,
SpiraTest, MKS, XStudio, Jenkins, Hudson, TeamCity, Bamboo, Robot
Framework, JUnit, Maven, …