ERROR: Content Element with uid "4532" and type "dce_dceuid16" has no rendering definition!
Testing needs to evolve and innovate to address the newly introduced non-functional risks that come with cloud computing. From the essential characteristics of cloud computing, a number of risks can immediately be determined. For example, broad network access means that most services are offered over the Internet, which introduces more severe security risks. A security error can allow a customer to see and possibly amend data that is not their own. A further example is that resource pooling means that devices are shared with other (unknown) customers, so response times of the service are affected by these other customers. This introduces a performance risk. How to cope with the phenomenon elasticity of the services? Does scaling up and down of capacity work efficiently and effectively in practice? How about BYOD (Bring Your Own Device)? How safe is the device and how safely does the user use it? Also local and international privacy legislation for the storage and processing of personal data requires attention. To determine which test measures are needed, all risks need to be mapped. Risk analysis shows which topics and objects need attention for testing, and to what extent. In fact what test measures are required? In this tutorial a pick and mix of Test Measures is presented, directly related to the both classical and special cloud risks. New solutions are introduced to tackle new risks that arise when implementing cloud computing and how to use innovative combinations of “traditional” and “new” testing techniques. One example (for this abstract): When testing the elasticity, three test techniques are combined: Load tests with a load profile to vary loads; Boundary value analysis at the boundaries of scaling up and scaling down and Process cycle test for the administrative process. What stands out in the cloud is the necessity of starting testing during the Selection of cloud services. Because continuity risks arise all the time, even after going live, continuous testing needs to be done. We shouldn’t scare away from Testing in Production: a continuous changing world needs continuous testing!
This tutorial starts with introduction of the essential characteristics of the cloud and the most popular implementation and service models. Then the most common (new) non-functional risks and needed measures for testing will be addressed and discussed.
Martin Pol has played a significant role in helping to raise the awareness and improve the performance of testing worldwide. He’s gained experience by managing testing processes and implementing and improving structured testing in many organizations in different branches worldwide. Martin was responsible for the creation of the structured testing approach TMapÒ (Test Management Approach) and the Test Process Improvement model, TPI Ò. Both TMapÒ and TPI Ò have become world standards. As the architect of the method Martin recently co-authored the best-seller “Testing Cloud Services”. Martin is a regarded presenter (keynotes, tutorials and track presentations) at conferences and training sessions throughout Europe, North and South America, India, China and Australia. He is still active in the testing practice every day. Additional info: http://www.polteq.com/en/about-polteq/martin-pol/
Kees Blokland joined Polteq in 2003 as test consultant. Before he joined Polteq he worked 14 years for Lucent Technologies R&D of which about 10 years in various test functions. As Polteq's R&D manager he develops Polteq’s vision on testing and provides international test consultancy. Kees is an experienced senior test manage and advices on test improvement and test outsourcing. He teaches a broad range of test classes, including ISTQB Advanced. He gave talks at various international test conferences (USA-Star, Eurostar, ChinaTest). Kees Blokland co-authored the well-received book “Testing Cloud Services”, available in Dutch, English and Chinese and shortly also in German.