SLAs and Cloud Testing

A test team’s job is to report test results, not set or guarantee that you will meet the SLAs.

In the rush to cloud services, with everything-as-a-service, you will hear people talking about SLAs. What is this about and what does it have to do with testing?

A Service Level Agreement, or SLA, is a contract a service provider promises for a defined level of service, such as response time, throughput or capacity.

When a customer signs up for service, the provider promises, in contract, certain levels of service. The most important aspect is usually availability. 

Availability is the ability to access the system. Everyone wants their service available all the time. This is an impossibility for both good and bad reasons. Good reasons – downtime, patches, new build migration and system upgrades. Bad reasons – system crashes, security problems – denial of service, network/infrastructure problems.

Downtime happens and SLAs are meant to provide a promise from the provider, of how available the system will be.

This is an important part of marketing, sales and contracts for any cloud service provider, from HP and Amazon to consumer products in the cloud like Netflix and Foursquare.

Gartner analyst Lyida Leong blogged that Amazon Web Services, which Gartner named a market-leader in infrastructure-as-a-service cloud computing, has the “dubious status of ‘worst SLA (service level agreement) of any major cloud provider.” She also wrote, “HP’s newly available public cloud service could be even worse.”

What are reasonable SLAs for availability? What is common? The answer differs based on the service. For example, many people use “4 9s” which represents 99.99% uptime:

Think about this: for four nines availability allows 1 minute downtime per week. Wow. How safe do you think it is for a company to guarantee this? In one full year, that means down time of less than an hour.

So what does this mean for testing? Testing SLAs is all about system performance testing; load testing, stress testing. It is measurement of the various attributes of the product; capacity, response time, against agreed upon standards. What you have to remember is a test team’s job is to report test results, not set or guarantee you will meet the SLAs.

Michael Hackett
Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems (Wiley, 2nd ed. 2003), and Global Software Test Automation (Happy About Publishing, 2006). He is a founding member of the Board of Advisors at the University of California Berkeley Extension and has taught for the Certificate in Software Quality Engineering and Management at the University of California Santa Cruz Extension. As a member of IEEE, his training courses have brought Silicon Valley testing expertise to over 16 countries. Michael holds a Bachelor of Science in Engineering from Carnegie Mellon University.

The Related Post

By Jez Humble and David Farley Continuous Delivery from Jez Humble and David Farley is an important contribution to the field of software development. It takes continuous integration to the logical conclusion and covers how to set up a continuous integration system, delving into everything from check-in to delivery to production. It doesn’t state you ...
As a software development company, what is your goal? What is the one thing you feel you need to do to ensure you have a job at the beginning of each wonderful work week? The answer is actually quite simple; You need to deliver a quality product. Like how I used the word simple? Although the answer I ...
Sauce Lab’s Perspective on Integration with Continuous Testing The term ‘DevOps’ implies that implementing an effective development and production workflow is as easy as developing the collaborative interaction between developers and IT operations. On the surface, DevOps may appear as a simple and straightforward idea but, as you will find out, there is more than meets ...
Making the leap to CT is easier than you think— follow this guide to transform your testing process No pain, no gain! Achieving Continuous Testing shouldn’t take a “Hans and Franz” attitude. It should be painless, more like a natural progression from implementing certain practices over time.
The book is an incredibly effective and valuable guide that details the risks that arise when deploying cloud solutions. More importantly, it provides details on how to test cloud services, to ensure that the proposed cloud service will work as described. It is a great start to the topic. The 6 chapters detail a paradigm ...
It’s no secret that the cloud is growing at an exponential rate. By 2016, two-thirds of the world’s server workloads will exist in the cloud. But according to Cisco’s 2012 Cloud Index, less than half of server workloads currently run in the cloud. Closing the gap between current capabilities and future requirements is a mission-critical ...
…On what you need to know before making the transition to EaaS 1. What are the main differences between cloud-based environments and cloud infrastructure? An environment is a collection of infrastructure elements working in conjunction to enable an application stack to work. For example, a simple 3-tier application, with a web front-end component, a business logic ...
Introduction Everything changes. It’s the only constant. The landscape of software testing is undergoing a fast and dramatic change driven by societal, business and technology changes that have placed software everywhere. Computing is ubiquitous. There is hardly anything today that doesn’t contain a CPU or information transmission capability, with software to drive it. From smart toasters ...
Aligning the Dev and Ops Teams DevOps as a philosophy has had as its centerpiece the principle that Dev and Ops teams need to align better. This is a people and organizational principle, not a process centric principle. To me this is more important when adopting DevOps than any other capability or tool. My last post ...
DevOps has been described as Agile on Steroids; DevOps has also been described as Agile for Operations/IT. I like both of those descriptions. Many organizations want Development, Test, and Operations teams to move to DevOps now. DevOps is a big topic, but DevOps is not the focus of this article. We will not be talking ...
  LogiGear_Magazine_June 2016_Testing in the New World of DevOps  
LogiGear Magazine June Testing in Continuous Delivery Issue 2017

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe