UI5con 2017 presentation Co-author: András Kónya

1. András Kónya, Lóránt Guth SAP Labs Hungary
June 30, 2017
Behavior Driven
Development with
OPA5 Automated Tests

2. 2
„I remember thinking “If only someone had told me that!” far more often
than I thought “Wow, a door has opened.””
Dan North
Benefits of Using BDD
 Reduces the communication gap between business and tech people
 Improves product quality
 Less customer complaints
 More progress & less stress for the team

3. 3
BDD cornerstones
Specification by example
Human readable, domain-
specific language
The BDD Framework

4. 4
Cucumber – The BDD Tool
Manual
Integration
Component/API
Unit
+
+ OPA5
$$$
$

5. About Technologies

6. 8
Architecture overview
Cucumber
Framework
Product Owner
Developer
OPA5
QUnit
Gherkin
JavaScript

7. 9
Business readable-writeable language
Cucumber understands and executes it
Based on the Given-When-Then pattern
Gherkin
Feature: Application test
Background: Open the application
Scenario: Create a new entity
Given Write MyAttribute to name field
When Click on Create button
Then Check entity with name MyAttribute
Cucumber
Framework
Product
Owner
OPA5
QUnit
Gherkin
Developer
JavaScript

8. 10
Cucumber
OPA5
Gherkin
Specification tool
–Uses Gherkin to describe the behaviour
Not a testing framework!
–JUnit, TestNG, QUnit are testing frameworks
Uses Step Definitions to translate Gherkin steps
Cucumber Cucumber
Framework
Product
Owner
OPA5
QUnit
Gherkin
Developer
JavaScript
this.register(
/^Click on the (.*) button$/i,
function(sButtonName, oPageObjects) {
oPageObjects.onAttributePage.iClickOnButton(sButtonName);
}
);

9. 11
QUnit based API for easy access and manipulation of UI5
controls
Helpful for writing automated tests for UI5 applications
OPA5
iClickOnButton: function(sButtonName) {
return this.waitFor({
controlType: "sap.m.Button",
viewName: viewName,
matchers: function($node) {
if ($node.getText() === sButtonName) { return true; }
return false;
},
success: function(oButtons) { this.pressOnButton(oButtons[0]); },
errorMessage: "Failed to click on the " + sButtonName + " button."
});
},
Cucumber
Framework
Product
Owner
OPA5
QUnit
Gherkin
Developer
JavaScript

10. Lessons Learned

11. 13
Keep it Business Readable!
Lessons Learned
Click on a button
–”Click on the New button”
–”Click on createButtonId button”
iClickOnButton: function(sButtonName) {
return this.waitFor({
controlType: "sap.m.Button",
viewName: viewName,
matchers: function($node) {
if ($node.getText() === sButtonName) { return true; }
return false;
},
success: function(oButtons) { this.pressOnButton(oButtons[0]); },
errorMessage: "Failed to click on the " + sButtonName + " button."
});},
matchers: function($node) {
if ($node.getText() === sButtonName)
{
return true;
}
return false;
},
id: sButtonId
Do not use element ID in the behaviour specification!

12. 14
Example
 Acceptance criteria is an essential part of the backlog items
 For complex behaviours (such as error handling), acceptance criteria definition is a huge
overhead for the Product Owner (PO). In this case, the following process is used:
 PO adds all required information to the backlog item
 Developer Team creates acceptance tests
 PO and Quality Engineer validates the tests and the test results
Result
 Deep understanding of the desired functionality while optimal workload balancing
Tailor Your Process!
Lessons Learned

13. 15
Example
Granularity of acceptance criteria must be chosen based on the nature of the functionality.
 Generally, a high-level formulation is recommended
 Use a more specific formulation critical scenarios with lots of possible outcomes (typically data
validation and error handling)
Result
 Acceptance tests can be used for regression
Choose the Perfect Granularity!
Lessons Learned

14. Thank you.
Contact information:
András Kónya
andras.konya@sap.com
Lóránt Guth
guth.lorant@sap.com
You are welcome to give feedback for this session
in the UI5con Event App