This document discusses behaviour driven testing (BDT) for multichannel enterprise applications. BDT focuses on testing user behavior across different channels like mobile, web, etc. It describes how user behavior remains the same regardless of the channel, and advocates testing behavior on each channel to validate user flows. The document outlines a testing approach using tools like Cucumber and shared backend logic. It also covers considerations like testing new channels, integration, and tool/test consumer.

1. Behaviour Driven Testing
for
Multichannel Enterprise Application

2. Contents
What is behaviour driven testing
What do we mean by multi channel applications
Testing Approach
Demo
Things to consider
Take Away

3. What this talk is NOT about ?
Behaviour Driven Development (BDD)

4. What this talk is about ?
Behaviour Driven Testing (BDT)

5. 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

6. Multichannel Enterprise Application

7. 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

8. 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

9. 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

10. 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

11. User Behaviour
remains the same irrespective
of the channel used

12. Architecture
UI Common
Backend
SOA / Web
Web
services
Services

13. Testing Entry Points
UI Common
Backend
Testing Entry
Points

14. User Flows
User Flow UI Common
Backend
ios
droi Web
d Services
web

15. User Behaviour
User Behaviour
User Behavior User Flow UI Common
Common
Backend
Backend
ios
droi Web
d Services
web

16. If we test User Behaviour
on each channel in-turn we test
the User Flows specific to that channel

17. Demo

18. Test Tools
Channel-
User Behaviour Specific UI Common
Mapping Backend
Frank io
Tools / Test Infrastructure
s
Cucumber Calab droid Shared logic
Specs ash
Web- web
driver

19. 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

20. Things To Consider …
Consumer of the tests
– Business
- QA team
Number of tests
– limited to the number of different user journeys available

21. Other Tools
Shim.js
Spoon.net
http://browsershots.org/

22. 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

23. Thank you !
Contact us:
sudeep@thoughtworks.com