Your SlideShare is downloading. ×
  • Like
  • Save
Whats In Your QA Tool Belt?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Whats In Your QA Tool Belt?

  • 911 views
Published

Presentation to Dallas Metro-SQA Group Oct, 2005

Presentation to Dallas Metro-SQA Group Oct, 2005

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
911
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Title slide
  • Portals added/modified Hardware and Software changes affected unexpected areas in Production Production changes were not deployed the same way they were in Test. Services were down after changes, “Monday AM triage” Customer complaints Potential violation of SLA terms VP said “There will be testing”; and so there was…

Transcript

  • 1. What’s In Your QA Tool Belt? Dallas Metro-SQA Presentation Walter Mamed Oct 12, 2005
  • 2.
    • Problem #1 – Branded Portal Testing and Migration
      • Off-The-Shelf (OTS) automation software & demo
    • Problem #2 – “Sunday Sanity” Manual Test Effort
      • In-House Built (IHB) automation software & demo
    • Problem #3 – Expanding on #1 & #2
      • Open Source S/W (OSS) automation software & demo
    • Summary/Benefits
    • Q & A
    • Networking @12:30
    Agenda
  • 3.
    • Branded Portals Background
    • ZixPort base provides configurable, semi-customized brands
    • Includes portal branding, images, links, and functionality
    • New Customer Portals
    • Customer modifications to existing Production Portals
    • Portal migration from .net49 to ZixPort 2.0 code base (2 nd Qtr 2004)
    • Branded Portal Manual Testing Effort Burden
    • Effort: 1 FTE & 1 QA full time, continuously each week
    • Frequency: Portals added and modified weekly
    • Limitation: QA could only handle max of 6 portals a week
    Problem #1 Portal Testing
  • 4.
    • New Branded Portal Automation Requirements
    • Handle sales prediction of 20 new portals per week
    • Portals added and modified weekly
    • Test upgrade of all 80+ portals from .net49 and ZixPort2.0; estimated at 10 weeks manual testing effort, and no new rollouts for 10 weeks during testing
    • Goal: Test future ZixPort releases in days; not weeks.
    • Tasks Identified to Meet Automation Goals
    • Solution required coordination among several departments
    • Development created QAPOP.dll to retrieve (pop) email
    • ‘ Client Services’ created Excel based client worksheets which included conversions to WinRunner data-table format.
    • QA developed WinRunner script driven from a data-table.
    QA Automation Requirements
  • 5.
    • Branded Portal Automation using WinRunner
    • Fast, accurate portal verification for new portals
    • Ability to add a greater number of new portals each week
    • Verifies logos, bitmaps, images, custom text
    • Metrics: 1 Full time person accomplished in 1/10 time for continuous weekly rollouts
    • Metrics: 10 week portal upgrade testing effort accomplished in 8 hours!!
    Solution #1: WinRunner (OTS)
  • 6.
    • Branded Portal Automation Demo
    • WinRunner (Lite Version – Not “Full Monty”)
    Solution #1: WinRunner (OTS)
  • 7. QA Manual Test Effort
    • Verify new features pushed to Production
    • Regression test existing Production functionality after changes
    • Effort: Medium number of tedious test cases across many portals
      • Six QA people needed for each Sanity run @ ~1.5 hrs each
    • Frequency: Any time changes are made in production
      • Hardware, Software, Network, ACL, etc...
      • Planned changes each weekend (Sunday Maintenance)
      • Hotfixes during week, after 5pm
      • As business grew, “Sunday Sanity” was more frequent
    • Limitation: Large after hours and weekend effort
      • Same tests run over and over
      • No consistent logging of dates, times, results, etc.
    Problem #2 “Sunday Sanity”
  • 8.
    • With the resource drain, frequency, off hours, volume and limitations… This effort screamed
    • “ AUTOMATION!!!”
    This QA Testing Burden…
  • 9.
    • WinRunner (Obvious Solution to #2)
    • Loses focus in Browser (WinRunner version 7.01)
    • Couldn’t attach to apps it started (invoke_application)
    • Therefore, not reliable for off-hour testing
    • Perl/Mechanize Automation (Actual Solution to #2)
    • Uses Perl “Mechanize” package.
    • Grabs the HTML directly
    • Able to easily follow links, fill in forms, search html
    • Also referred to as “screen scraping”
    Problem #2 “Sunday Sanity”
  • 10.
    • Pros
    • Abstracts out Perl programming
    • Set of common, easy to use functions
    • Reads in test file (text), executes each command
    • Keeps a log of commands and results
    • Provides combination of Web and Perl commands
    • Able to call other tests
    • Cons
    • Requires a serious Perl programmer initially (in QA clothing!)
    • No automatic redirection
    • Cannot specify individual buttons
    • Could not use some Windows functions (like file attachments)
    • Browser-less testing
    Solution #2 Perl-Mechanize
  • 11.
    • Mechanize Code Example
    • #, Lexus Sanity
    • Get, https://www.lexusfinancialofsc.com
    • PrintTitle
    • FindText, Register for online access to your LFS , Pass, Fail
    • SetField, User, support@zixcorp.com
    • SetField, password, ******
    • SubmitForm
    • Get, https://www.lexusfinancialofsc.com/my_lfs/access_account/AccountSummary.do
    • PrintTitle
    • FindText, Welcome To My LFS Account, Pass, Fail
    • FollowURL, Mail Center
    • FindText, Welcome to the Mail Center, Pass, Fail
    • FollowURL, Inbox
    • FindText, Status, Pass, Fail
    • FindText, Subject, Pass, Fail
    • FindText, Date Received, Pass, Fail
    • FindText, Expiration Date, Pass, Fail
    • FollowURL, Compose
    • PrintTitle
    • FindText, Email Address:, Pass, Fail
    • FindText, Account:, Pass, Fail
    • FindText, Subject:, Pass, Fail
    • FindText, Message:, Pass, Fail
    Solution #2 Perl-Mechanize
  • 12.
    • Results For Problem #2
      • Executes defined well documented “Sunday Sanity” tests
      • Utilizes Windows Task Scheduler every day at 6am
      • “ Sunday Sanity” accomplished in 1 hour.
      • Six person effort accomplished with one person, less than five minutes (when no errors) on Sunday morning
      • “ Sunday Sanity” on demand for Hotfixes (rarely needed now)
      • Any QA person can run and verify results
      • All required functionality checked
      • Results logged and saved in time-stamped files
    Solution #2 Perl-Mechanize
  • 13.
    • Perl-Mechanize Demonstration of “Sanity Test”
    • “ Sunday Sanity” Automated Testing using Mechanize
      • Scheduled execution 6am on Sunday
      • Scheduled execution 6am on Weekdays (less Billing)
      • Example of a test run summary
      • Example of drilling down into test results
    Solution #2 Perl-Mechanize
  • 14.
    • Combined limitations of WinRunner and TestMech
    • WinRunner
      • Loses focus in Browser
      • Couldn’t attach to apps it started
      • Babysitting execution of test runs.
      • GUI Map issues with new releases
    • TestMech
      • Requires a serious Perl programmer initially
      • No automatic redirection
      • Cannot specify individual buttons
      • Could not use some Windows functions (like Msg attachments)
      • Browser-less testing
    Problem #3
  • 15.
    • Making Fortunate Discoveries by Accident
    • Software Quality Engineering Training Programs Brochure
      • Script Programming for Testers
      • Brett Pettichord (the guy in the cowboy hat – of course!)
      • Web Application Testing In Ruby (Watir) – pronounced water
      • Ruby Scripting Language
    • Danny Faught - Tejas Consulting
      • Posted he liked Watir over Samie circa 12/04
    • Curiosity killed the cat...
      • Subscribed to Watir User Forums
      • Observed a serious commitment by the developers
      • Developers AND users responsive to “newbie questions”.
      • Feature development prioritized by user community demand
      • Releases were fairly steady (~2-3 months)
    Serendipity Strikes!
  • 16.
    • Initial Steps
    • Read the install procedures – clear and fact full
    • Downloaded Ruby and Watir
    • Ran unit tests supplied with Watir – Failed tests!
    • Read FAQs – how to configure pop-up handling…
    • Reran unit tests – All PASSED!
    • All this in an 1 ½ hours – I was impressed.
    • Within an hour, I had a script that could log into a Production portal.
    • Possibilities appeared endless!
    • Seeing the unit tests work and examining the code that performed them was very insightful.
    Watir Investigation
  • 17.
    • Production Rollouts on the horizon
    • New feature releases and fixes for the two largest ZixPort customers, health insurance payors.
    • Personal desire to reduce several hours of post production testing and increase test coverage.
    • Able to automate Payor#1 pseudo sanity fairly quickly for all portals.
    • Able to automate Payor#2 pseudo sanity with exception of two portals (due to hidden objects)
    • Watir Bonus! – Log into the two Payor#2 portals manually and Watir could “attach” to the browser and complete automated testing. – way cool!
    Watir Enthusiasm Grows
  • 18.
    • Continued Watir Development
    • Modularized functions to use against both portals.
    • Leveraged Prod tests against Payor#2 Staging Environment
    • Added more Staging tests and pushed coverage to Test
    • Continued adding test cases in Test Environment
    • Reversed trend from Test, Staging & Production with next Prod Release!
    • Now the serious coding begins…
      • Added Send Mail code
      • Added Receive Mail code
      • Attachments can now be performed (need to follow-thru)
    Watir Progress
  • 19.
    • Pros
    • Very reliable, repeatable & dependable
    • Execution stability extremely high
    • Uses IE Browser
    • Browser can be minimized during testing
    • Multiple scripts can be run simultaneously on the same machine without interference.
    • Other activities can be performed while Watir is running.
    • Comes with a great editor SciTE (Scintilla Text Editor)
    • Leverages a mature OO platform – Ruby
    • Great Developer and User support forum
    • Best of all – it’s Open Source (feel free to contribute!)
    Solution #3 Watir - Pros
  • 20.
    • Cons
    • Cannot perform Netscape and FireFox Browser testing (Selenium to the rescue?)
    • Handling of popup dialogue boxes continually in flux (WinHelper, AutoIT & what-next?)
    • New Watir Release changes may cause some heartache (migration woes – I desired access to “hidden objects” which required minor coding changes across all scripts)
    • Primarily intended for Unit testing, being adopted by QA worldwide for functional and regression testing.
    • Several potential logging mechanisms, but none are a clear winner going forward.
    Solution #3 Watir - Cons
  • 21.
    • Benefits
    • Increased test coverage, reduced test execution time
    • Reduces repetition of monotonous tests
    • Reduces overtime to a fairly tolerable level.
    • Reduced post-deployment test time for large customers (from 4 Hours to 1 Hour)
    • No problems have been detected by customer
    • Customer confidence in ZixPort products continues to grow
    • Walt has fun coding and doing test automation!
    Solution #3 Watir - Benefits
  • 22.
    • Crystal Ball (Future plans)
    • Continue increasing test coverage
    • Need ability to log test results to time-stamped files
    • Need ability to post to Test Director
    • Modularize and consolidate functions
    Solution #3: Watir
  • 23.
    • Watir - Demo
    • Single Execution
    • Multiple Execution
    • Minimized Execution
    • All of the above…
    Solution #3: Watir Demo
  • 24.
    • Watir home page
        • http://wtr.rubyforge.org
    • Wtr-general Archives
        • http://rubyforge.org/pipermail/wtr-general
    • Ruby
        • http://rubyforge.org
    • Special thanks to our host! – NerdBooks!
      • Spread the Word!
    Watir - References
  • 25.
    • What’s in the ZixCorp QA Tool Belt?
    • Each test automation tool fills a valuable niche.
    • Each tool complements the other.
    • All three are used on a daily basis.
    • All three contribute to increased test coverage and reduced test cycle times.
    • ZixCorp is able to meet the level of quality and the high-availability as required by our Customer SLA’s.
    Summary
  • 26.
    • Test Automation Benefits:
      • Fast
      • Accurate
      • Repeatable
      • Reliable
      • More extensive tests
      • Results are stored
      • Improved use of QA time under existing budget and time constraints
    • Q & A
    Test Automation Benefits