Cloud testing
Lua error in package.lua at line 80: module 'strict' not found. Cloud testing is a form of software testing in which web applications use cloud computing environments (a "cloud") to simulate real-world user traffic.
Contents
Overview
Cloud Testing uses cloud infrastructure for software testing.[1] Organizations pursuing testing in general and load, performance testing and production service monitoring in particular are challenged by several problems like limited test budget, meeting deadlines, high costs per test, large number of test cases, and little or no reuse of tests and geographical distribution of users add to the challenges. Moreover, ensuring high quality service delivery and avoiding outages requires testing in one's datacenter, outside the data-center, or both. Cloud Testing is the solution to all these problems. Effective unlimited storage, quick availability of the infrastructure with scalability, flexibility and availability of distributed testing environment reduce the execution time of testing of large applications and lead to cost-effective solutions.
Need for cloud testing
Traditional approaches to test a software incurs high cost to simulate user activity from different geographic locations.[2] Testing firewalls and load balancers involves expenditure on hardware, software and its maintenance.[3] In case of applications where rate of increase in number of users is unpredictable or there is variation in deployment environment depending on client requirements, cloud testing is more effective.[4]
Types of testing
Stress
Stress Test is used to determine ability of application to maintain a certain level of effectiveness beyond breaking point. It is essential for any application to work even under excessive stress and maintain stability.[5] Stress testing assures this by creating peak loads using simulators. But the cost of creating such scenarios is enormous. Instead of investing capital in building on-premises testing environments, cloud testing offers an affordable and scalable alternative.
Load
Load testing of an application involves creation of heavy user traffic, and measuring its response. There is also a need to tune the performance of any application to meet certain standards. However a number of tools are available for that purpose.
Performance
Finding out thresholds, bottlenecks & limitations is a part of performance testing.[6] For this, testing performance under a particular workload is necessary.[7] By using cloud testing, it is easy to create such environment and vary the nature of traffic on-demand. This effectively reduces cost and time by simulating thousands of geographically targeted users.
Functional
Functional testing of both internet and non-internet applications can be performed using cloud testing. The process of verification against specifications or system requirements is carried out in the cloud instead of on-site software testing.
Compatibility
Using cloud environment, instances of different Operating Systems can be created on demand, making compatibility testing effortless.
Browser performance
To verify application's support for various browser types and performance in each type can be accomplished with ease. Various tools enable automated website testing from the cloud.
Latency
Cloud testing is utilized to measure the latency between the action and the corresponding response for any application after deploying it on cloud.
Steps
Companies simulate real world Web users by using cloud testing services that are provided by cloud service vendors such as Advaltis, Compuware, HP, Keynote Systems, Load Impact, Neotys, RadView and SOASTA. Once user scenarios are developed and the test is designed, these service providers leverage cloud servers (provided by cloud platform vendors such as Amazon.com, Google, Rackspace, Microsoft, etc.) to generate web traffic that originates from around the world. Once the test is complete, the cloud service providers deliver results and analytics back to corporate IT professionals through real-time dashboards for a complete analysis of how their applications and the internet will perform during peak volumes.
Keys to successful testing
- Understanding a platform provider's elasticity model/dynamic configuration method
- Staying abreast of the provider's evolving monitoring services and Service Level Agreements (SLAs)
- Potentially engaging the service provider as an ongoing operations partner if producing commercial off-the-shelf (COTS) software
- Being willing to be used as a case study by the cloud service provider. The latter may lead to cost reductions.
Applications
Cloud testing is often seen as only performance or load tests, however, as discussed earlier it covers many other types of testing. Cloud computing itself is often referred to as the marriage of software as a service (SaaS) and utility computing. In regard to test execution, the software offered as a service may be a transaction generator and the cloud provider's infrastructure software, or may just be the latter. Distributed Systems and Parallel Systems mainly use this approach for testing, because of their inherent complex nature. D-Cloud[8] is an example of such a software testing environment.
For testing non-internet applications, virtual instances of testing environment can be quickly set up to do automated testing of the application. The cloud testing service providers provide essential testing environment as per the requirement of the application under test. The actual testing of applications is performed by the testing team of the organization which owns the application or third party testing vendors.
Tools
Leading cloud computing service providers include, among others, Amazon, Advaltis, 3-terra, Skytap, HP and SOASTA.[9] Some of the tools for cloud testing include :
Benefits
The ability and cost to simulate web traffic for software testing purposes has been an inhibitor to overall web reliability. The low cost and accessibility of the cloud's extremely large computing resources provides the ability to replicate real world usage of these systems by geographically distributed users, executing wide varieties of user scenarios, at scales previously unattainable in traditional testing environments. Minimal start-up time along with quality assurance can be achieved by cloud testing.
Following are some of the key benefits:
- Reduction in capital expenditure[10]
- Highly scalable[11]
Issues
The initial setup cost for migrating testing to cloud is very high as it involves modifying some of the test cases to suit cloud environment. This makes the decision of migration crucial.[12] Therefore, cloud testing is not necessarily the best solution to all testing problems.[13]
Legacy systems & services need to be modified in order to be tested on cloud. Usage of robust interfaces with these legacy systems may solve this problem.[14] Also like any other cloud services, cloud testing is vulnerable to security issues.
The test results may not be accurate due to varying performance of service providers’ network and internet.[15] In many cases, service virtualization can be applied to simulate the specific performance and behaviors required for accurate and thorough testing.
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
