Vijay & Supriya - Test your service not your ui
Upcoming SlideShare
Loading in...5
×
 

Vijay & Supriya - Test your service not your ui

on

  • 988 views

Test your service not your ui - presented in vodQA - THE TESTING SPIRIT! on Oct 7, 2010 in ThoughtWorks, Pune

Test your service not your ui - presented in vodQA - THE TESTING SPIRIT! on Oct 7, 2010 in ThoughtWorks, Pune
Organization: ThoughtWorks

Statistics

Views

Total Views
988
Views on SlideShare
988
Embed Views
0

Actions

Likes
0
Downloads
19
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Vijay & Supriya - Test your service not your ui Vijay & Supriya - Test your service not your ui Presentation Transcript

  • Test your service not your UI By Vijay and Supriya
  • Meet Tejal Tejal– Six yrs in QA Automation Expert Tools that she uses Selenium, Watir and QTP Attends Conferences Nickname – “Bug Hunter”
  • How does Tejal test? Browser Selenium U I L A Y E R
  • Tejal wants to test the movie booking flow
  • Her automation approach
  • What’s troubling Tejal?
  • Tests are High Maintenance • Change in UI
  • Tests are Flaky • Page load handling • Ajax
  • Longer Time to execute 100 tests take 3 hours to execute
  • Tool Limitations Handling custom controls Handling modal dialogs
  • Tejal needs Ideas
  • Tejal attends vodQA in Pune
  • Tejal meets Ram And explains to him her sob story
  • Meet Ram Ram – 8 yrs in QA Automation Expert Tools used – Selenium, QTP, Watir, Fitnesse Likes to try new things
  • How does Ram test? Browser Selenium (For Smoke testing only) U I L A Y E R Service Layer Regression tests written at service layer DB Database Layer
  • Ram’s automation approach SearchMovieService(City, TheatreName, MovieName, Date, Time, NoOfSeats). SelectSeats(A1, A2, A3). MakePayment(CardNo, CardExpiry, Pin). VerifyConfirmation();
  • What are the benefits?
  • Shorter time to execute • No browser/application startup • Devoid of elements • Tests run “super fast”
  • Only needs an IDE No tool limitations xUnit framework
  • Tests are Low Maintenance • Business process seldom changes
  • Manual Exploratory testing • Automating tests is faster • More time for exploratory testing
  • Wait, Tejal has some questions …
  • What should be covered as part of Service testing?
  • What happens to UI Functionality testing?
  • Are you not duplicating tests created by Devs?
  • Tejal is now happy
  • And tejal started testing happily ever after  The End
  • Our Experiences • Changing mindset wasn’t easy • 20 Regression E2E tests which run in ~4 minutes • Entire regression suite would run after every developer check-in • Tests were written before UI was ready Developer Speak Service tests by our QAs caught some really good bugs. – Ashish Sharma (Developer)
  • To Summarize… Service testing is a concept worth exploring Treating the service as an application which deserves its own suite of tests Both need to co-exist
  • Questions