How to evolve your

MANUAL testing team into

an AUTOMATION team

with codeless automation

▪March 2018

Speakers

2

Sheli AshkenaziSr. Product Manager

Experitest

Dhiraj RajotiaSr. Sales Engineer

Experitest

Ruth ZamirDirector of Marketing

Experitest

Agenda

3

The rising need for automation

Creating a codeless / low code automation environment

Demo

01

02

03

Summary & Q&A04

7 min

20 min

10 min

10 min

4

Every company is a

TECHNOLOGY company

Business priorities impact development and delivery goals

5

Source: Forrester: Master DevOps For Faster Delivery Of Software Innovation, 2017

6

Focus on speed, business agility and risk reduction

Paradigm shift in software/ application development

Agile CI/CDDevOps

Testing is a bottleneck to short release cycles

7

Source: GitLab 2018 Global Developer Report

Shorter cycles = More cycles

*Same or more features in app = More regression testsMore cycles

The testing bottleneck

8

9

How can we achieve high automation with our existing teams?

Drive for more automation requires organizational change

Performance & Volume

5%

Environment and Data10%

25%

, 60%

Automation Testers & Software engineers in test

Exploratory testers

Performance & Volume10%

Environment and Data20%

Automation Testers10%

Manual testers60%

Case study: North American financial institute

10

Increase automation with your existing teams

Source: ITJobsWatch

Don’t compete for scarce resourcesRetain valued employees with domain knowledge and organizational expertise

Share of Test Automation engineer job postings out of R&D/IT job postings

Agenda

11

The rising need for automation

Creating a codeless / low code automation environment

Demo

01

02

03

Summary & Q&A04

7 min

20 min

10 min

10 min

12

BDD principles

Creating a codeless automation environment based on BDD abstraction

Scenarios recorded in ubiquitous language*These are the feature

acceptance tests

Design specifies features using behaviors:

user story scenarios

Design done by collaborative team: Business-Dev-Test

• Write the feature acceptance tests first

• Write them collaboratively and in a way everyone can understand

Feature:Scenario:Given:And:WhenThen:

* Example uses Gherkin, but can be any agreed format

13

DevTest workflow using Cucumber

Scrum teamDefine behaviors in

ubiquitous language >> feature files

DevelopersWrite code

Automation engineerCreates step definitions

TestersWrite feature files in Gherkin syntax

Automation project / Continuous testing

14

How does this create codeless automation?

Testers

Write and maintain use case (feature files) using Gherkin

Automation engineer

Write and maintain step definitions

15

An example of a BBD & Cucumber based test

Feature file Step definition

Written in Gherkin “steps” Created in code (Java, Ruby…)

Feature: Login to EribankCorrect login credentials open application home page presenting the account balance

Scenario: Login with valid credentialsGiven Eribank application is openWhen I enter username as “company”And I enter password as “company”And I clicks login buttonThen I see the application home pageAnd I see the account balance

Scenario: Login with in-valid credentialsGiven Eribank application is openWhen I enter username as “compan”And I clicks login buttonThen I see wrong username or password page

Agenda

16

The rising need for automation

Creating a codeless / low code automation environment

Demo

01

02

03

Summary & Q&A04

7 min

20 min

10 min

10 min

17

Tester

• Creates a test: login to Eribankapplication

• Execute on a remote device

• Uses Cucumber, SeeTest Digital assurance lab

• Pre-configured step definitions

What we will demo

Automation engineer

• Creates step definition

• Uses Appium Studio for Eclipse, SeeTest Digital assurance lab

18

Demo –Tester

19

20

21

Demo –Automation engineer

22

Agenda

23

The rising need for automation

Creating a codeless / low code automation environment

Demo

01

02

03

Summary & Q&A04

7 min

20 min

10 min

10 min

BDD and codeless testing impact on testing speed and quality

24

Higher test maintainability

• Reusable “step definitions” simplify test modification and debugging: update once, impact entire test suite.

Use natural language to write tests

• Testers with domain expert can quickly write tests with no need to code.

• Easy to identify test scenario and ensure coverage

25

• No of applications: 6

• Automation engineers: 12

• Developers: 12

• Testers (no coding knowledge): 18

Case Study: North American financial institute

Feedback cycle shortened by 50%

Technical debt reduced by 60%

Tests & documentation ready from day 1

• Implemented BDD Using Cucumber

• Manual testers trained on Cucumber

• Scrum teams : Product, Test, Dev • not automation engineers

• No code is committed without tests • automation engineers are gatekeepers

• Full automation suite executed nightly

27

Questions?

28