behavior driven testing for multichannel enterprise applications

23
Behaviour Driven Testing for Multichannel Enterprise Application

Upload: bamdad-dashtban

Post on 05-Dec-2014

1.096 views

Category:

Technology


3 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Behavior Driven Testing for Multichannel Enterprise Applications

Behaviour Driven Testing

for

Multichannel Enterprise Application

Page 2: Behavior Driven Testing for Multichannel Enterprise Applications

Contents

What is behaviour driven testing

What do we mean by multi channel applications

Testing Approach

Demo

Things to consider

Take Away

Page 3: Behavior Driven Testing for Multichannel Enterprise Applications

What this talk is NOT about ?

Behaviour Driven Development (BDD)

Page 4: Behavior Driven Testing for Multichannel Enterprise Applications

What this talk is about ?

Behaviour Driven Testing (BDT)

Page 5: Behavior Driven Testing for Multichannel Enterprise Applications

What is Behaviour Driven Testing ?

Approach to look at Bigger Picture

Helps drives Testing development

Uses Behaviour Driven Tools

Majorly useful for testing Multichannel

Applications

Page 6: Behavior Driven Testing for Multichannel Enterprise Applications

Multichannel Enterprise Application

Page 7: Behavior Driven Testing for Multichannel Enterprise Applications

Buy a train ticket using iPhone

As a iPhone user

I want to buy a train ticket

So that I can travel to a place of my

interest

Page 8: Behavior Driven Testing for Multichannel Enterprise Applications

Buy a train ticket using Android

As a android user

I want to buy a train ticket

So that I can travel to a place of my

interest

Page 9: Behavior Driven Testing for Multichannel Enterprise Applications

Buy a train ticket using Website

As a web user

I want to buy a train ticket

So that I can travel to a place of my

interest

Page 10: Behavior Driven Testing for Multichannel Enterprise Applications

User behaviour – buy a train ticket

As a user

I want to buy a train ticket

So that I can travel to a place of my

interest

Page 11: Behavior Driven Testing for Multichannel Enterprise Applications

User Behaviour

remains the same irrespective

of the channel used

Page 12: Behavior Driven Testing for Multichannel Enterprise Applications

Architecture

SOA / Web servicesWeb Services

UI Common Backend

Page 13: Behavior Driven Testing for Multichannel Enterprise Applications

UI Common Backend

Testing

Entry

Points

Testing Entry Points

Page 14: Behavior Driven Testing for Multichannel Enterprise Applications

Common Backend

UIUser Flow

User Flows

ios

droid

web

Web Services

Page 15: Behavior Driven Testing for Multichannel Enterprise Applications

Common Backend

UIUser Behavior

Common Backend

UIUser Behaviour

User Flow

User Behaviour

ios

droid

web

Web Services

Page 16: Behavior Driven Testing for Multichannel Enterprise Applications

If we test User Behaviour

on each channel in-turn we test

the User Flows specific to that

channel

Page 17: Behavior Driven Testing for Multichannel Enterprise Applications

Demo

Page 18: Behavior Driven Testing for Multichannel Enterprise Applications

Tools / Test Infrastructure

Common Backend

UIChannel-Specific Mapping

User Behaviour

Frank

Calabash

Web-driver

ios

droid

web

Cucumber Specs

Shared logic

Test Tools

Page 19: Behavior Driven Testing for Multichannel Enterprise Applications

Things To Consider

Where to start in the process

– user journey on 1 channel is complete

Where these tests fit in / are useful

– for multichannel applications

- when a new channel is introduced

– in the regression cycle

Page 20: Behavior Driven Testing for Multichannel Enterprise Applications

Things To Consider …

Consumer of the tests

– Business

- QA team

Number of tests

– limited to the number of different user journeys

available

Page 21: Behavior Driven Testing for Multichannel Enterprise Applications

Other Tools

Shim.js

Spoon.net

http://browsershots.org/

Page 22: Behavior Driven Testing for Multichannel Enterprise Applications

Take Away

Write Once Run Any where

User Behaviour remains the same irrespective of the

channel used

If we test User Behaviour on each channel in-turn we

test the User Flows specific to that channel