O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Behavior Driven Testing for Multichannel Enterprise Applications

1.038 visualizações

Publicada em

Publicada em: Tecnologia
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Behavior Driven Testing for Multichannel Enterprise Applications

  1. 1. Behaviour Driven Testing forMultichannel Enterprise Application
  2. 2. Contents What is behaviour driven testing What do we mean by multi channel applications Testing Approach Demo Things to consider Take Away
  3. 3. What this talk is NOT about ? Behaviour Driven Development (BDD)
  4. 4. What this talk is about ? Behaviour Driven Testing (BDT)
  5. 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. 6. Multichannel Enterprise Application
  7. 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. 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. 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. 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. 11. User Behaviourremains the same irrespective of the channel used
  12. 12. Architecture UI Common Backend SOA / Web Web services Services
  13. 13. Testing Entry Points UI Common BackendTesting Entry Points
  14. 14. User FlowsUser Flow UI Common Backend ios droi Web d Services web
  15. 15. User BehaviourUser BehaviourUser Behavior User Flow UI Common Common Backend Backend ios droi Web d Services web
  16. 16. If we test User Behaviour on each channel in-turn we testthe User Flows specific to that channel
  17. 17. Demo
  18. 18. Test Tools Channel-User Behaviour Specific UI Common Mapping Backend Frank io Tools / Test Infrastructure sCucumber Calab droid Shared logicSpecs ash Web- web driver
  19. 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. 20. Things To Consider … Consumer of the tests – Business - QA team Number of tests – limited to the number of different user journeys available
  21. 21. Other Tools Shim.js Spoon.net http://browsershots.org/
  22. 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. 23. Thank you ! Contact us: sudeep@thoughtworks.com

×