1. Testing on Cloud (In the context of TaaS) Srinivasan Desikan
HP Confidential

2. Evolution of Testing Services
Testing as a service (TaaS) Operate at these levels
Testing as a project (TaaP) Operate at these levels
HP Confidential

3. TaaS fits in at different Models/Gen’s
Granularity of Service
5th Gen: Solution Testing, Interop Testing, Capacity planning, Competitive analysis …etc
4th Gen: Func/Feature test, Compatibility tests, WBox / BBox testing …etc
3rd Gen: Create Test plan, Create Test specs, Execute tests, Automate …etc
Service Maturity
Note: Next Gen service is not exclusive and includes deliverables defined by previous Gen as appropriate.
HP Confidential

4. Paradigm Shift To Testing as a Service
From To
Project oriented
Build to last
Prolonged development cycles
Team silos & contribution
Tightly coupled
Product oriented
Known implementation and project skill based
HC based Cost structure
Service oriented
Build to change
Incrementally built and delivered on demand
Enterprise contribution
Loosely coupled
Customer (internal & External) oriented
Abstraction and testing CoE based
Utilization based cost structure
HP Confidential

5. Evolution of test infrastructure & resources
Level of Automation
Cloud based model where test teams use Zero foot print infrastructure
Agile service model where test infrastructure virtualized; test teams formed dynamically
Testing service model where both test teams and infrastructure centralized
Datacenter model where all test teams share a centralized data center
Set of machines shared between few test engineers based on teams they work
Dedicated machines and teams for testing
End-to-End SDLC / process automation
Image/Env mgmt, SDLC automation
Setup, build, test, test mgmt automation
Setup, build, test automation
Setup, Test automation
Minimal test automation
Level 0: Dedicated
Level 1: Shared
Level 2: Centralized
Level 3: Modeled & CoE
Level 4: Virtualized
Level 5: Cloud
HP Confidential

6. Testing on cloud – Salient points
Test Process
Process for sharing resources across teams based on datacenter practices (ITSM, ITIL)
Process automation as against test automation
Process to segregate test infrastructure and machines needed for testing – Test infrastructure is unshared and machines for testing comes from cloud
Automation
Zero footprint on SUT automation process – Web based products preferable
Setup and virtual machine setup part of automation goals
Test management
Centralized test management for all products using tools
Performance & stress testing on cloud is still a challenge
Clear demarcation between functional & non-functional test requirements
HP Confidential