Letter from the Editor – December 2013

If you are reading this issue, you are probably aware of the impact on the business world of cloud computing.

Most people do not have a good grasp on what the cloud is or how people and products can use it. BTW, you are already a cloud user. If your email is stored somewhere “on the internet”, like YahooMail, Gmail, Hotmail – you are using the cloud. If you use an online tax service, TurboTax or others – you use that software-as-a-service in the cloud. This is where they calculate your tax and store your tax data.

If you use or share Google docs, store or transfer files using Dropbox, or stream movies on Netflix, you are interacting with the cloud.

From SalesForce to Groupon to LinkedIn, the rapid growth of all things mobile is driving cloud development. Many different forces are converging to push applications, products and services into the cloud. 

As is often the case for new technologies, test teams are at the end of the information trail. What cloud architecture issues need to be tested, what services need to be tested, what SLAs need to be tested? The explosion of devices and appliances impact compatibility and UI testing.

We need to better understand what the cloud is, what people mean when they use phrases like a cloud of APIs, personal cloud, hybrid cloud, etc.

On the other hand, remember – cloud is delivery, not development. The differences between cloud development and other development implementations is a very hot topic in the dev. world. Forrester’s 10 Cloud Predictions for 2013 include Developers waking up to the fact that development isn’t all that different in the cloud.

Many testers say testing things in the cloud is no different than web testing, thick server, thin client testing. It’s no different, or the difference is in the specific testing issues like scalability, security, performance. There is no difference in functionality, cross browser/mobile UI and usability, localization- most aspects of testing remain the same. Cloud is delivery, not development.

In this issue we try to demystify the cloudy cloud. The articles and the glossary, in addition to past articles and publications on cloud computing give you a broad and better understanding of the testing implications around cloud computing.

In my article I outline how to approach SLAs when working in the cloud; SmartBear’s Ole Lesmar looks at some special considerations that should be applied to applications running in the cloud; Ben Rothke reviews the book Testing Cloud Services: How to Test Saas, Paas and Iaas; Chris Riley of Cloudshare tackles issues relating to software and hardware licensing for cloud projects and LogiGear’s Joe Luthy emphasizes that the right skills and experience is essential for designing tests for large-scale cloud deployments.

You can view past cloud articles here and our 2014 editorial calendar here.

We’re always open to new submissions!

As holidays approach and we finish 2013, we very much look forward to a bigger, brighter, happier coming new year!

Michael Hackett

Senior Vice President, LogiGear Corporation

Editor in Chief

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

I was just recently at a company that had a beautiful test architecture, framework, and Cucumber with tons of well-automated tests. But there was no good test management on top of the Cucumber tests, and they did not do a good job tagging the tests. Although almost everybody on the team could write and maintain ...
Big and complex testing. What do these terms conjure up in your mind? When we added this topic to the editorial calendar, I had the notion that we might illustrate some large or complex systems and explore some of the test and quality challenges they present. We might have an article on: building and testing ...
This is our first Trends issue in our 10- year history. Trends are important to help foresee what is on the horizon and coming next.
In the November 2011 issue: Mobile Application Testing, I began my column with the statement, “Everything is mobile.” One year later the statement is even more true. More devices, more platforms, more diversity, more apps. It boggles the mind how fast the landscape changes. Blackberry has been kicked to the curb by cooler and slicker ...
A lot has changed since I began staffing test projects. From hiring college students and interns for summer testing programs, to building networks of offshore teams around the world, and from having 24-hour work schedules to having instant crowdsourced public beta or bug bounty testing—things have changed.
Continuous Testing… what is it? When we first decided to do a magazine issue dedicated to the DevOps practice of Continuous Testing, I joked with someone: “It’s about testing continuously.” And their reply was: “Yeah. What else would it be?” I was joking, but clearly the joke didn’t land. Continuous Testing is about testing continuously, ...
Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, ...
API testing– an old school technology gets way cool again. APIs and testing them is nothing new; the technology has been around for decades. The most basic definition of an API is an exposed function— a producer (person or company) writes a function and exposes it so that others, consumers, can use it. We copy ...
A while ago, I helped start a Software Quality Certificate Program as a part of the Software Engineering Program at the University of California, Santa Cruz Extension in Silicon Valley. I was on the Board of Advisors. While putting the curriculum together, a few people suggested a Measurement and Metrics course. Since I was teaching ...
Testing tools – very important, very often overlooked, and very often where mistakes are made. First, the most common mistake people make about tools is thinking tools are only about test automation! False. Automation tools are merely one type testing tool. We will try to balance this issue between test automation tools and other test ...
Testing Embedded systems and testing the Internet of Things could each have their own issue of LogiGear magazine. But these days they are referred to presupposing knowledge of the other, so we thought it would be a good idea to tackle the two together in this issue to give a broad understanding of the landscape ...
The Greek philosopher Heraclitus of Ephesus (c. 500 BCE) is credited with saying, “The only constant is change.”   This is a statement that, more than 2,000 years later, still holds true. Today, we are in a time of great change. Everything is in flux. The fact is, we are always in a state of change even if ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe