This document discusses functional testing using Cucumber. It recommends using Cucumber's Gherkin language to write feature files with scenarios and step definitions. The document outlines their workflow of 8 master releases per year with functional testing done after each sprint. It discusses Cucumber terminology and provides recommendations for writing better Cucumber tests as well as examples of Cucumber reports. Both pros and cons of using Cucumber are listed.

2. KEEP YOUR APPLICATIONS TUNED
Functional Testing
by
Kristof Debruyne & José Luis Santos

3. facilitator facilitator
knowledge

8. EMPOWER
ONLINE TEAMS01 ACTIVATE YOUR
DIGITAL CUSTOMERS02 ACTIONABLE
INSIGHTS03 CONTINUOUS
AUTOMATION04
Adobe Experience Cloud
Personalization
Analytics
Full Stack Web apps
APIs
Java / JS
Machine learning / Big
Data / Monitoring
DevOps practices /
Automated FT /
Continuous Integr.
CUSTOMER JOURNEYS SUPPORT

9. EMPOWER
ONLINE TEAMS01 ACTIVATE YOUR
DIGITAL CUSTOMERS02 ACTIONABLE
INSIGHTS03 CONTINUOUS
AUTOMATION04
01
02
03
04

10. #StopTheBullshit

11.  E-services migration
 AEM, Apache Sling, Apache Jack Rabbit (JCR), Apache Felix (OSGi), Slice,
JMX, AngularJS
 Initial goal of functional testing
 Goal: Improve overall code stability
THE MISSION

12. OUR WAY OF WORKING (1/2)

13.  6 teams
 8 master releases per year / every 3 weeks maintenance release
 1 master release = 3 sprints
 DoD and functional testing
OUR WAY OF WORKING (2/2)

14. SETUP

15.  Gherkin language
 CLI-runner
 Simple life cycle
• Alternative for JBehave / JFunc
• 3-layer: feature, scenario, step
CUCUMBER

16.  Feature
 Scenario
 Step definition
 Hook
TERMINOLOGY
 Tag
 Cuke
 Glue

17. FEATURE DRIVEN

18. LIFE CYCLE

19. RECOMMENDATIONS (1/2)
 Imperative vs declarative
 clear separation (scope) of scenarios
 Don’t put meta data in step defs
 Group tag scenario’s

20. RECOMMENDATIONS (2/2)
 Context driven (no state in step definitions)
 Never -> Thread.sleep(x)
 Performance as important factor
 Scenario outlines (tables)

21. REPORTING (1/3)

22. REPORTING (2/3)

23. REPORTING (3/3)

24. PROS AND CONS
PROS CONS
+ Regression out-of-the-box (return of
investment)
+ Quality assurance tool to improve
overall code quality
+ Acts as JavaScript test tool (if you don’t
have KarmaJS, JasemineJS, etc …)
+ Rebase verification
+ Test mobile development (emulated
but works pretty well) / multiple
browsers
+ Nice reporting (pdf + screenshots)
+ Other stuff (test toggles, AEM
components, etc …)
- Time consuming (full time job)
- High setup cost
- Inconsistency of mock data results in
bad tests
- Team effort (all stakeholders!)
otherwise it is useless

25.  https://cucumber.io
 http://cucumber.github.io/api/cucumber/jvm/javadoc
 https://en.wikipedia.org/wiki/Behavior-driven_development
RESOURCES