Untitled

[galloptesting]

What role does AI play in QA?

Artificial Intelligence-based testing can offer several benefits to testers in the form of enabling automation in writing test cases, improving test coverage, making predictive analysis, and identifying bugs early, and saving significant costs thereon.

Quality testing has become a critical factor in ensuring that a software application delivers customer satisfaction. It involves assessing and analyzing the software application under certain conditions to know its threshold and attendant risks when implemented. However, with software build life cycles turning more complex and delivery turnarounds reducing, QA testers need to identify any inherent glitches in the application quickly and effectively. Thereupon, the information is passed on to the development team to fix the glitches and turn the application worthy of being delivered or implemented.

The complexity of any software application under development has become more challenging due to the focus on quick releases. So, what used to take a month for delivery has become a weekly affair with updates factored in almost on a daily basis. This has made the job of software testers all the more challenging and has created conditions to make testing smarter, efficient, accurate, and predictive. No wonder AI-based testing has become the go-to area for testers to implement a continuous automated and precision-based testing process. In fact, AI testing has begun to play a critical role in quality control for a host of business and industry verticals. It helps to set in motion a slew of measures that is predictive, accurate, and objective. By freeing up human effort, AI-led quality assurance speeds up the SDLC to achieve outcomes as mandated by Agile and DevOps methodologies.  

Further, given that human testers have subjective biases, especially in a manual testing setup where the quality of testing can change according to the quality of the testers, Artificial Intelligence app testing delivers on parameters like speed, cost, accuracy, performance, safety, and scalability, seamlessly and effectively. AI can not only find glitches in the software application but perform root cause analysis to understand the source of such glitches.

Benefits of using AI in QA testing

Since orchestrating test automation across CI/CD pipelines has become challenging, AI testing services are used to enable smart testing in applications that have multiple dependencies, resources, and technologies. The benefits of using AI-based testing are as follows:

Automation of writing test cases: One of the challenges QA testers face while conducting test automation is writing test cases. They often end up writing large test cases to detect a minor bug thereby impacting test efficiency. AI test automation can ensure the writing of precise test cases quickly and accurately. Besides, when developers/testers write test cases, instead of choosing the most efficient option – the one that generates the least redundant data, they write test cases that they are comfortable with. AI, on the other hand, can choose the most efficient test option where there would not be bottlenecks, manual involvement, or redundant data.

Improve overall test coverage: AI-driven testing can expand the scope of testing by looking into the memory and file contents, data tables, or internal program states. This way it can determine if the software application is behaving as expected. AI can execute several test cases in every test run, which is not possible with manual testing. 

Identify bugs early and deliver cost savings: Bugs or glitches can be very expensive to fix if identified later in the SDLC. However, AI test automation can offer instant feedback to the developers about the presence of bugs and deliver significant cost savings. It is important to remember that the cost of fixing bugs after product release can be four to five times expensive than the ones identified in the SDLC.

Predictive analysis: Artificial Intelligence can analyze the existing customer data to predict how customers’ browsing habits and needs would evolve. This helps developers and testers to be a step ahead of users’ choices and offer quality products or services in alignment with their expectations. With AI-ML testing, the test platforms get better at analyzing user behavior and making precise predictions.

Conclusion

In a day and age where going digital is the ultimate goal for enterprises to reach out to their customers and be competitive, AI-powered platforms have become a tangible reality. AI-based testing helps to optimize test automation and let the tests to self-heal and execute. It helps in automating more areas of testing such as UI testing and visual validation. By analyzing large volumes of data, Artificial Intelligence can create comprehensive and precise test cases to validate the smallest bugs in the system.

Resource:  

James Daniel is a software Tech enthusiastic & works at Cigniti Technologies. I'm having a great understanding of today's artificial intelligence services that yields strong results and always happy to create valuable content & share thoughts. 

Article Source: www.sooperarticles.com

[galloptesting]

Benefits of Test Automation CoE | IP-led Tool Agnostic Test Automation Framework

Cigniti’s test automation CoE leverages Selenium as a tool of choice for automating web application testing, performing functional regression automation, and developing & maintaining automated test suites.

https://www.cigniti.com/test-automation-coe/#methodology

[galloptesting]

How does Security Testing help in validating the Healthcare Ecosystem

Security testing has assumed a critical role in the healthcare ecosystem with several benefits. These include validating the mechanism for the transmission and storage of data, identity management, and building trust and confidence for the software application.

The healthcare ecosystem’s dependence on digital technologies to deliver better services to patients and other stakeholders has made it vulnerable to security threats. If statistics are to be believed then healthcare companies across the world are going to cough up a whopping $6 trillion in damages due to security breaches in 2020 (Source: PhoenixNAP.) Modern-day healthcare applications store sensitive patients’ data, which has often led to medical identity theft necessitating the need for rigorous software application security testing. The critical patients’ data may include identity details, payment information, bank account details, history of morbidity, and insurance details, among others. The breach of any of this information can be lethal and devastating, both for the patients and the healthcare facility.  

Why is the healthcare security system important?

Cybercriminals are targeting critical patient information to steal identities using methods or tools like phishing, malware, or ransomware. To pre-empt such attacks a robust application security testing strategy needs to be put in place with the following guidelines.

Top-most priority to be given to ensure security for the vital facets

The application security testing methodology should remodel the framework for data security, verification, audit logging, and many more

The other aspects of security testing would include business logic testing, data validation testing, session management testing, DOS testing, Ajax testing, configuration management testing, and OWASP   testing to check for vulnerabilities such as SQL injection and XSS.

What are the types of healthcare security testing?

Security testing covers a range of tests to verify and validate the robustness of the healthcare application and its ability to fend off various security threats.

Penetration testing: In this type of testing, ethical hackers try to gain entry into the healthcare application by exploiting its vulnerabilities. The process performed manually or using automated testing, gathers information about the application in terms of the possible entry points. Thereafter, the hacker attempts to break into the application and verifies its level of system protection.

Application-level testing: Also known as app-level testing, the technique ensures the software application doesn’t execute any malicious actions. Here, specific security-related scenarios are validated by conducting functional testing.

DDoS testing: In this type of interactive application security testing, simulated DDoS (Distributed Denial of Service) attacks are conducted with real traffic to understand the level of protection offered by the application to thwart DDoS attacks.

Security code review: It mitigates potential security vulnerabilities in the software code early on and prevents costly and time-consuming fixes later. It serves as a final review to check the application’s safety before launch.

How does software application security testing benefit the healthcare domain

Security testing for the healthcare domain gives insight into the robustness of the healthcare application and its ability to face cyber threats. The benefits of employing software application security testing include:

Protecting PHI: This type of testing Identifies and fixes all vulnerabilities associated with Protected Health Information (PHI) and checks if PHI complies with the HIPAA standards.

Data storage validation: It checks if the data storage mechanism, in encrypted or plain-text form, is safe and secure. Besides, it analyses the security solution, encryption methods, and data management techniques and helps to detect any security issues with the application’s database.

Data transmission validation: Software applications transmit data across cloud, mobile devices, and email, which should be properly encrypted to prevent any unauthorized access at any stage.

Identity validation: Detects vulnerable access points that could be exploited by hackers, especially the areas covering identity management. The software application security testing helps to mitigate any breach of patient privacy and strengthen the mechanism for identity management.

Risk assessment before deployment: Once the application with security-related vulnerabilities is deployed, it may cause havoc in the form of security breaches. The application security testing services offer the opportunity to identify and fix all security-related vulnerabilities in the application. This ensures the application is bereft of any security issue and protects the customer from carrying out any type of financial transaction.

Builds trust and confidence: Security testing ensures the application is compliant with the HIPAA standard. This helps to build the trust of your clients in the application and boost its brand equity.

Conclusion

The cybersecurity dimension is expanding at a phenomenal rate coupled with growing incidences of security breaches. To restore customer confidence and prevent such incidences,healthcare security testing should be conducted rigorously.

Article original Source: https://medium.com/

[galloptesting]

Software Quality Assurance company | Business Continuity Planning

Read how Cigniti is supporting Global organizations across the industries to serve their customers with utmost efficiency amidst the COVID-19 global crisis.

Read how Cigniti is supporting Global organizations across the industries to serve their customers with utmost efficiency amidst the COVID-19 global crisis.

[diyatestingupdates-blog]

5 Reasons Why Your Application Testing Strategy Needs ‘Agile’ Intervention.

In an increasingly IT enabled digital landscape software applications are being launched at an alarming rate. This is primarily to thwart competition and garner the elusive customer pie by businesses. This development can be bracketed into two dimensions. One, customers have become tech savvy and want their software applications to be of the best quality. They also want the applications to be updated from time to time underpinned by the emerging technologies and threats.

The second dimension is about companies trying to keep pace with the changing customer preferences and market dynamics. Companies are indeed finding it challenging to meet the twin objectives of bringing applications (or their updates) at a faster rate and ensuring their quality each and every time. The latter requirement brings in the need for quality testing, which in the traditional waterfall model is not effective enough. To meet the evolving quality testing challenges, businesses have begun to implement Agile testing as the new testing approach.

The reason why Agile testing has gained ground amongst the testing community, not to speak of the other stakeholders, is the inadequacy of the traditional waterfall testing model. In a traditional testing setup, the testing is carried out post the development of an application. Since the testing here is primarily manual, its full rigour across deliverables and platforms is not carried out to its entirety. Moreover, it is difficult to carry out manual testing on a repetitive basis for all variables in each and every test environment. This reduces the test coverage area quite drastically.

In the final analysis, the traditional way of testing leaves a lot to be desired and lets glitches to go unchecked. Also, even when the glitches are identified and sent back to the development team for correction, the process consumes time. Moreover, the fact that the rewritten code needs to be tested again increases the lead time and cost of the project. The outcome of a poor test coverage area, lack of communication between the testing and development teams, lack of proper usability testing, and unrealistic schedules leads to the delivery of a poor quality application with less or no takers.

Agile test automation, on the other hand, is more coherent, time and cost saving, focused and helps in better identification and elimination of glitches. It helps in breaking silos between the development and testing teams, thus, accelerating the time to market with better quality applications. Let us delve into the five reasons in which Agile intervention can help the application testing strategy.

#1 Enhanced Quality: The Agile testing strategy involves the commencement of testing alongside the development process. It is a shift-left testing approach that validates the quality of software at the beginning of the SDLC. Here, testing forms a part of the development phase wherein the bugs are fixed simultaneously with the development of an application as opposed to the traditional model. This helps in reducing the SDLC and enhancing the product quality. In this model, the testing team gets early insights into the quality issues and helps the development team with better integration of the software codes.

#2 Comprehensive testing: Since the Agile testing strategy involves the use of automation, the Agile testing experts write test cases to carry out repetitive tests for a range of dependencies. Thus, they effectively coordinate and communicate with the development team in identifying new glitches in the codes. The test automation process helps in the conduct of complex and repetitive tests thereby increasing the test coverage area. This significantly increases the chances of identifying glitches and improves the quality of the application.

#3 Accelerated time to market: Agile application testing identifies the presence of bugs quickly in the development phase thanks to its iterative model. The glitches are corrected and the code gets integrated in the overall end-to-end software application faster. Since the development and test cycles are reduced, the application is released into the market quickly. Moreover, the release of updates is done faster in the Agile set up leading to a better user experience.

#4 Saving of cost: Since Agile application testing leads to a shorter product lifecycle and fewer test reruns, the development and testing cost comes down. Also, in an Agile test setup that incorporates automation, the software test tools and other resources can be centralized. This helps in the better procurement of resources leading to their better utilization and maintenance.

Moreover, as opposed to the traditional waterfall testing model where post development testing and integration increases the development cost, the Agile way is considerably better. Since the unit testing of codes is carried out alongside development, the quality of software post development is substantially better. As the software products are delivered faster with smaller lead times, the business saves costs. This helps the application in maintaining its competitive edge in the market.

#5 Better productivity: The Agile set up involves the presence of business stakeholders. This leaves a lesser room for confusion or ego issues that the development and testing teams suffer from in the traditional testing model. Since the Agile teams are better organized and cohesive as far as planning and implementation of the tasks are concerned, they are more efficient and productive. In the Agile setup, the teams have the authority to go about their business by the consent of the client thus increasing the ownership of the project.

Conclusion

The Agile testing methodology is more flexible, dynamic, and faster to address the requirements of testing. It is being adopted on a greater scale by enterprises as affirmed by Gartner (about 60 – 80%) and is far better than the traditional waterfall model of testing.

This Article is originally published at Medium.com, 5 Reasons Why Your Application Testing Strategy Needs ‘Agile’ Intervention.

[galloptesting]

How can 'Digital Testing' help you to make your next business idea successful and market ready?

[galloptesting]

Cigniti’s Quality Engineering services ensure that testing shifts left and begins way ahead in the overall SDLC, ensuring maximum test coverage and quality

[galloptesting]

Do You really need DevOps for Digital Assurance and Testing?

Can DevOps as a preferred methodology bring real value for Digital Assurance and Testing? Check out our latest post.

[galloptesting]

Do Test Accelerators really speed up ERP Testing?

Can Test Accelerators bring value to your ERP testing process? Check out our latest post and let us know your views.

[galloptesting]

Do Test Accelerators really speed up ERP Testing?

Can Test Accelerators bring value to your ERP testing process? Check out our latest post and let us know your views.

[galloptesting]

This blog discusses the growing significance of Microservices Architecture and how DevOps can add value for Microservices Testing, and help accelerate it.

[galloptesting]

How to Build the Right Selenium Testing Strategy in 4 Ways.

The need for software testing in the entire SDLC process has increased for various reasons. Ranging from ensuring the quality of software…

[galloptesting]

How to Build the Right Selenium Testing Strategy in 4 Ways.

The need for software testing in the entire SDLC process has increased for various reasons. Ranging from ensuring the quality of software…

[galloptesting]

Key to the future of smart city – Internet of Things

A smart city is conceived as a huge ecosystem of interconnected organs of a city brought about by embedded electronics, softwares, sensors, and actuators using wireless or other networks working in a seamless way to provide better services to the citizens. The organs can include services like fire, police stations and hospitals, power generation and distribution centres, residential buildings, businesses, courts, municipalities, libraries, schools, colleges, administrative units, transportation system, traffic management, and many others. In a smart city good use of computer based networks can be used to bring about the following:

·         Prompt response in cases of emergencies like fire, natural disasters, rioting, accidents, etc.

·         Betterment of services like health, education, etc.

·         Better waste management by municipalities

·         Better traffic management through suitable signalling and parking arrangements

·         Ensure proper distribution of power and reduce leakages

·         Better coordination amongst a multitude of transport services

·         Better management of schools, colleges, libraries, etc.

·         Better monitoring of air quality and optimal use of natural resources like water

Smart cities are the need of the hour; as urban population density is expected to grow exponentially in the coming years. As population increases the pressure on limited resources is bound to grow leading to conflicts. Smart cities would ensure equitable distribution of resources in the most efficient way. As there will be less wastage or leakages in the services offered the citizens will be better served leading to a better quality of life. To bring the concept of smart cities into reality Internet of Things or IoT will play an all encompassing role.

IoT enables physical infrastructure like buildings, vehicles and all other objects to communicate and exchange data with each other. They can do so with the help of embedded softwares, actuators, sensors, thermostats and other gadgets through wireless network protocols like LAN, WAN, PAN. As the proper functioning of IoT becomes a prerequisite for different organs of a smart city to function in a seamless manner, the testing of IoT ecosystem becomes inevitable.

IoT testing services can include the following:

Functional testing: Here individual components like applications, sensors, actuators, etc. are tested for efficient outcomes. It also tests if the communication bandwidth is adequate for faster transmission of data signals.

Interoperability of systems test: It covers testing of various devices and software systems to ensure they operate across different platforms with compatible versions.

Security testing: Checks if gadgets and services follow security protocols, and adhere to privacy norms.

Usability testing: Checks systems and processes from the users’ perspective to ensure they meet user requirements and lead to a better user experience.

Conclusion:

As IoT ecosystem is part of the basic architecture of smart cities, its proper functioning needs to be ensured. Hence, IoT testing is an absolute must to usher in a throbbing smart city.

Michael works for Cigniti Technologies, which is the world's first Independent Software Testing Services Company to be appraised at CMMI-SVC Level 5, and an ISO 9001:2008 & ISO 27001:2013 certified organization.

[galloptesting]

5 skills in Security Testing you need to build for 2017

We have tried to put together a brief overview of five areas of security testing expertise that would be more in demand in the coming year. The article discusses a range of aspects such as Machine Learning, a powerful security measure that operates by Artificial Intelligence, depicts damage control mechanism or Incident response plan, the potent Sandbox tool for Malware analysis, Whitelisting as opposed to blacklisting, Identity and access management measures like PAM, PKI. The essence of the specified areas of software security testing are brought to the reader for their quick identification.

As cyber security has become one of the biggest areas of concern both for the individual and the enterprise, more number of security testing experts are required.

According to industry statistics, by 2019, a massive 6 million security testing experts will be needed and there would only be 4 to 5 million professionals with right skills.

Some of the key domains of security testing skills that are going to be in demand big time are lined up here.

1.       Machine learning

For advanced form of threat, machine learning solutions are emerging strong. In this technology the machine is not something that works as programmed but grows its abilities through self-learning, just like human brain. It is in line with artificial intelligence and still is the most sophisticated form of technology devised.

2.       Incident response plan and Malware analysis with Sandbox

As we prepare to detect and resist threats, we must also have detail plan of action when security has been transgressed. To minimize the degree of damage, Incident Response plan is a powerful security testing measure.

This area of security skill is to do with damage control in the aftermath of data breach or any other attack on cyber security. Knowing the deft use of right tools, a skilled Incident response planner is able to rise to the emergency situation to address and manage the harm in the best possible manner.

Many big corporations are investing in Incident Response and threat intelligence professionals to build better fortresses and responses against cyber breaches.

3.       Malware analysis with Sandbox

Malware is the big old enemy and cannot get detected by regular antivirus systems. It can trigger a wide range of disruptions in automated systems. Sandbox is a very strong mechanism of detecting malwares from unverified or untrusted sources. Works as a standalone, Sandbox ensures no harm to the host system. A 60 % increase in Malware analyst position noticed in the last two years and is expected to grow manifold.

4.       Whitelisting

For a long time it was a cumbersome task to blacklist the ever-growing and ever-changing army of viruses. The new whitelisting security approach has proved to be more apt. Whitelisting applications allow only pre-approved programmes and services while closing all other probabilities of deceptive applications.

5.       Privileged Access Management

Security testing is about building an integrated solution for controlling all privileged or authentic accounts. Managing authentication and authorization of a user, who needs access to a system is a security testing skill of great worth.

6.       PKI  

Public Key Infrastructure (PKI) is another kind of integrated authentication system comprising computer systems, policies and standards. It creates, distributes or cancels digital keys and certificates.

Authentication of identity and Access is essential for an organization’s smooth functioning, and this is a key expertise to be built.

Conclusion

Security is a prime concern and more the threats or vulnerabilities, better are the efforts to fight them with newer and smarter technologies. Both businesses and governments depend heavily on security testing experts and will continue to do so for some obvious operational and performance reasons.

Michael works for Cigniti Technologies, which is the world's first Independent Software Testing Services Company to be appraised at CMMI-SVC v1.3, Maturity Level 5, and an ISO 9001:2008 & ISO 27001:2013 certified organization.

[galloptesting]

6 Best Practices for implementing Test Automation

Automated Software Testing is programmable according to exact testing specifications, enables user environment simulation, simplifies repetition in a cost effective, time saving, resourceful, and highly effective manner. It is superior in regression testing, and effortlessly manages time consuming, and iterative tests in the software development lifecycle. Regression testing zones in on different bugs and categorizes them to deliver superior quality results.

It is often programmed in-house by testing firms to be in sync with precise testing protocols for new software products, and concurrently observes latest security protocols. Additionally, it is super effective in executing Graphical User Interface (GUI) testing. Experts resort to testing the newly developed software product in a simulated user defined environment, which is followed by troubleshooting any bugs in the responsive platform of the GUI.

Functional Test Automation makes this two-fold process fast, seamless and perfect.

Before any software or application is released into production, it has to be tested rigorously. The process which involves software tools to run pre-scripted tests on the target application is referred to as Test Automation. As this method involves a very limited set of scripts, it can simplify the testing process for manufacturers. There are several benefits of Test Automation:

It does not consume as much resources as unit testing

This test can be carried out innumerable times

The Automation tools keep track of every new bug and thus remain upgraded

It can radically improve test results through reruns

Specific user environments can be simulated through well categorized keystrokes and mouse clicks

Instead of manually testing out every user scenario, they can be programmed into a unique software, which can then carry out automated tests on other new software, thus reducing the time and effort involved in the process.

1.      It is better to have a dedicated team

There is a vast difference between manual testing and Test Automation. From the tools used to the time and effort required, Test Automation is a full-fledged responsibility. It is always advisable to build a dedicated team for Test Automation, including one automation architect and several automation engineers working with him or her.

2.      Choose Your Tools practically

Know your company's system and resources inside out. When choosing your testing tool, make sure it runs well with the platform your company usually runs on and that it also integrates well with the resources and framework the test application is based on. This helps keep the costs down and also makes the process seamless and future proof.

3.      Do not rely solely on the Automation Tool

The tools cannot work alone if the testers are not familiar with them. While building a team make sure your testers are acquainted with the way the automation tool is supposed to work. The tools might be incapable of testing complex processes by themselves if the engineers are not skilled enough.

4.      Know the Application Being Tested

It is very important to have a clear knowledge of the application or software you are assessing. This can help you choose the tools so that the tests run effectively. For example, in case of a web application, knowing the browser can be a great time saver; for a desktop application, the programming language is a crucial part, as unsupported tools can lead to undue complications.

5.      Test Automation cannot be 100%

Complete test automation is impossible. The main purpose of Test Automation is to prevent repeated testing for the same thing so that manual testers can save time and effort and instead focus on newer testing scenarios and bugs that automated tests cannot handle.

6.      It is better to avoid GUI Automation when possible

GUI automation can be a tricky process and can be difficult to proceed with, especially at times when the interface has changed. Thus, if it is possible to run a test using an alternate method such as a command line input, GUI automation should be avoided in order to ease the process.

Conclusion

Test automation can be rewarding and can ease the testing process for the entire team. However that can only be the case if a proper strategy is followed. From the tools, infrastructure, to the people handling the test, every bit plays a vital role. Understanding the business objectives of the organization, and knowing the application under test (AUT) can save a lot of time, effort and money.

Michael works for Cigniti Technologies, which is the world's first Independent Software Testing Company to be appraised at CMMI-SVC v1.3, Maturity Level 5, and an ISO 9001:2008 & ISO 27001:2013 certified organization.

[galloptesting]

An insight into Functional Testing in a Cloud Environment

Performing Functional Testing in Cloud environment is not too different from that in regular test environments. However, for cloud environments, the test cases need to be rewritten in order to keep them Cloud ready. Unless new features have been added as a part of the cloud hosting strategy, there is no difference in business process validation.

Functional Testing is generally performed to ensure that the services provided by the software are consistent with its specifications. Functional Testing can be performed through two perspectives –

-      Requirement based testing: In this approach the requirements are first prioritized and then the tests are prioritized accordingly. This is done to ensure that the most critical tests are covered in the process.

-      Business process based testing: In this approach, the testing scenarios involved in the day to day business of the system are described.

Functional Testing in a Cloud environment involves testing of all the features and functions of the system, which includes both the hardware and the software of the system. It is generally conducted on a completely integrated software platform in order to check its compliance with the requirements. In the cloud environment, the process of verification is carried out against a system of specifications and requirements on a Cloud instead of an on-premise software testing platform. Functional Testing may take various forms in a Cloud environment.

-      System Testing: This testing is performed in order to test the behavior of the system within its own boundaries. It is critical to prove that the system functions as it has been designed, inputs and outputs are as expected and the overall quality is ensured.

-      Integration Testing: Integration testing verifies that the Cloud environment will not be detrimental to the existing system and will successfully work with the current infrastructure and the environment.

-      User Acceptance Testing: This testing is performed in order to ensure that the Cloud environment supports the business requirements and the user accepts the Cloud solution.

-      Interoperability Testing: Most of the applications are now cross-platforms and must meet business critical requirements such as data exchanges, etc. Through interoperability testing, testers try to verify that the programs work with equal efficiency on a variety of platforms.

-      System Verification Testing: It is more of a technical testing, which includes code audits, documentation revisions and the testing of hardware as well as software components under normal and stressful conditions.  

The difference between an end-to-end testing and system integration testing is very clear in a Cloud environment. A complete end-to-end testing mainly focuses on testing combinations of business processes and systems by recreating real business scenarios. The following potential scenarios need to be validated through the testing processes.

-      Data Inconsistency

-      Data misinterpretation due to human dependencies

-      Consistency of database schema

Conclusion

Testing and Cloud are both large domains in their own respect. Functional Testing with respect to the cloud environment involves both traditional and new methods. For software applications provided on clouds, it is important to perform functional as well as non-functional testing. Software applications hosted on the Cloud  pose additional testing challenges, which can get  resolved with  a systematic and comprehensive approach towards test planning.