Testing Software Services
Upcoming SlideShare
Loading in...5

Testing Software Services






Total Views
Views on SlideShare
Embed Views



1 Embed 1

http://athomestdtest.xyz 1



Upload Details

Uploaded via as Microsoft PowerPoint

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.

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

Testing Software Services Testing Software Services Presentation Transcript

  • Testing in the Cloud Our experience of testing software that is “out there”
  • Introduction
    • The Presenters
      • Paul Selway – [email_address]
      • Scott Rostal – [email_address]
    • What is “The Cloud”?
    • What is different / the same for cloud testers?
    • Testing Philosophy / Test phases
    • What was easier / harder than expected?
    • Key success factors
    • Questions?
  • What is “The Cloud”?
    • Internet (“The Cloud”) accessible solution
    • Off-premise multi-tenant architecture
    • Accessed via a browser (PC or Wireless)
    • Delivered as Software as a Service (SaaS)
    • Common cloud companies are:
    • Google, Amazon, WorkDay, and Salesforce
  • What things are the same about testing cloud solutions?
    • Requirements coverage based testing
    • Risk-based structured test approach
    • Test Plan / Test Phases
    • Test Cases / Test Data / Test Automation
    • Defect Management / Functional Test
    • Use of off-shore resources / Virtualization
    • Politics {Quality / Schedule / Resources}
  • What is different about testing cloud solutions?
    • Shared multi-tenant test environments
    • Security (Test User IDs / SSO)
    • Integration of on/off premise systems
    • Performance / volume test
    • Defect isolation
    • Documentation of “Out Of the Box” reqs
    • Release Management
  • Project Philosophy
    • Risk-based structured testing approach {std}
    • “Exploratory Testing” to discover the out of the box cloud solution features {non-std}
    • Data Migration – Moving legacy data off premise {Non-Std}
    • Performance / volume test only our new infrastructure – not the cloud app {Non-Std}
  • Testing Phases Overlapping Test Phases Unit / Code Coverage Inspections & Reviews Exploratory & System UAT & Pilot End-To-End Integration A mix of waterfall (with heavy phase overlapping), and iterative delivery Load & Performance Data Migration
  • What was harder than expected?
    • Isolating the architectural components for a performance test
    • Understanding that a cloud solution vendor delivers new releases which you have to take!
    • Accepting that you have a “black box” in your environment
    • Determining who owns defects
    • Data Migration Mock Runs
  • System Integration Architecture
  • What was easier than expected?
    • Getting the IT leaders to embrace change
    • Overlapping Test phases
    • End User Adoption
    • Use of off-shored test resources
      • Functional
      • Performance
      • Data ETL
  • Key Success Factors
    • Learn the “Out of the Box” cloud application features, security model, and configuration capabilities
    • Understand the holistic system architecture
    • Understand the migrated test data
    • Establish tight communications with the vendor
  • Questions?
  • Contact Info
    • Scott Rostal – [email_address]
      • Performance Lead, Thrivent Financial for Lutherans
    • Paul Selway – [email_address]
      • President, Red Path Consulting Group