Thursday, October 7, 2010

Cloud Application Testing

Parul Mody

Vijay Khatke SQA – BMC Software

Legal Notice

The information contained in this presentation is the confidential information of BMC, Inc. and is being provided to you with the express understanding that without the prior written consent of BMC, you may not discuss or otherwise disclose this information to any third party or otherwise make use of this information for any purpose other than for which BMC intended.

All of the future product plans and releases described herein relate to BMC’s current product development considerations, which are at the sole discretion of BMC and are subject to change and/or cancellation at any time. BMC cannot and does not provide any assurance as to whether these plans will result in any future releases of the nature described. These future product plans should not be viewed as commitments on BMC’s part and thus should not be relied upon in customer purchase decisions.

What is “The Cloud”? Cloud Layers How is „Cloud Testing‟ different? What is easier / harder than expected while testing? Take Aways Q & A

AGENDA

What is Cloud?

• Sharing computing resources

• No local servers or personal devices to handle

applications.

• Key features include:

• Agility

• Cost

• Multi Tenancy

• Scalability

• Maintenance

• Metering

• Accessed via a browser

• Delivered as Software as a Service (SaaS)

• Common cloud companies are:

Google, SalesForce, Amazon, and WorkDay

Deployment Models

• Public Cloud

Cloud

Public

Private

• Private Cloud • Hybrid Cloud

Hybrid

Layers

Client

Application

Platform

Infrastructure

Server

Usage Model

Requirements coverage based testing

Test Plan / Test Phases as per desired model

Test Cases / Test Data / Test Automation

Defect Management / Functional Test

Use of off-shore resources

Plans {Quality / Schedule / Resources}

What stays…

Similarities

Multi Tenancy

Cloud Platform Knowledge

Compatibility of application features with the platform (understanding

platform limitations)

Security (Test User IDs / SSO)

Integration of on/off premise systems

Performance / volume test

Release Management

Whats different..

Differences

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 whether defect is at application or platform level Data Migration

Challenges

Throughput and render time Browser dependency

Non cached Cached

Real time usage (Keynote)

Performance Testing- Scope

What was easier than expected..

• Use of off-shored test resources

• Functional

• Performance

• Localization

• Ease of environments setup/ configuration

• Simple patch/ upgrade process

• Limited Business impact during upgrades

• Limited requirement for multiple environment

combinations

•Minimal onboard training for new QA resources

• End User Adoption

Ease

• 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 cloud vendor

Take Aways

Q & A