Business white paper. Best practices for implementing automated functional testing solutions

Transcription

1 Business white paper Best practices for implementing automated functional testing solutions

2 Table of contents Contents 3 Introduction 3 Functional testing versus unit testing 4 The pros and cons of manual functional testing 4 Why automate functional testing processes? 5 The benefits of automated functional testing 6 How to identify candidates for automated testing 6 How to determine the ROI of automated testing 7 Evaluating automated testing software: what to look for 7 About HP functional testing solutions 8 Checklist: five keys to successful automated testing 8 Summary

3 Abstract: Today s enterprises need to conduct thorough functional testing of their mission-critical applications to verify that all business processes work as expected. By implementing automated functional testing, your company can dramatically increase both the speed and accuracy of your testing processes, providing a higher return on investment (ROI) from software projects while dramatically cutting risk. This paper presents a brief overview of the advantages and challenges of automating functional testing to help structure your thinking about how best to approach test automation. It also summarizes the key features and benefits of the HP automated functional testing software HP Unified Functional Testing software (formerly HP QuickTest Professional) and HP Service Test software some of the industry s most popular and powerful automated software testing solutions. The paper concludes with a brief overview of HP Business Process Testing software and presents a checklist of the five keys to successful automated testing. Introduction There is no question that rigorous functional testing is critical to successful application development. The challenge for your developers, QA teams, and management alike is how to speed up testing processes and increase accuracy and completeness without breaking your already tight budgets. By automating key elements of functional testing, your company can meet aggressive release schedules, test more thoroughly and reliably, verify that business processes function correctly, and ultimately generate higher revenue and customer satisfaction from your online operations. Yet the prospect of automating functional testing raises new concerns: What are the costs of automating the testing processes and what is the ROI? Which applications/processes are candidates for automated testing and which are not? Will new training be required and how will that impact current development project schedules? What is the proper methodology for automating a testing effort? What is involved in maintaining automated tests? When comparing test automation products, which features are most important? These and other issues need to be fully examined and understood before test automation projects are initiated. Functional testing versus unit testing Functional testing provides the ability to verify that applications work as they should that they do what users expect them to do. Functional tests capture user requirements in a useful way, give both users and developers confidence that the business processes meet those requirements, and enable QA teams to verify that the software is ready for release. Functional testing is complementary to but quite different from unit testing. Simply put, unit tests indicate whether the code is doing things right; functional tests tell whether the completed application is working correctly and providing the proper functionality. Unit tests are written from the code developer s perspective, while functional tests are written from the end user s and business-process perspective. 3

4 The pros and cons of manual functional testing Though the benefits of automated testing are many, there are some situations where manual testing may make sense from a functional or cost perspective. To make the decision between automated and manual testing, it is important to understand the strengths and weaknesses of manual functional testing processes. Some of the disadvantages of manual testing include: Manual tests take too long. Limited IT resources combined with tight delivery schedules make manual testing simply too time-consuming to be effective in meeting business objectives. With manual testing, your testers and developers must tediously document each step of a test case and then manually execute each test and reproduce defects, which rapidly consume valuable time and resources. Manual tests provide incomplete coverage. The proliferation of platforms, operating systems, client devices, business processes, and data sets wreaks havoc on manual testing processes. As testers begin to combine multiple data sets, operating environments, and business processes, they create an explosion in the number of test cases that need to be executed to verify the functionality of an application. This makes it very difficult to perform verifications of all of the multiple permutations. And, when development fixes are introduced, manual regression testing takes too long to make complete regression tests practical. Manual tests introduce higher risk. Manual testing processes are subject to a higher risk of mistakes and oversights than computerdriven processes. People get tired, they make errors entering data, they don t always code the tests correctly, and they don t always have the time to test everything that should be tested. But for some environments, manual testing may be an appropriate choice. For example, manual testing may be appropriate for applications that are under heavy development, that frequently change their UI or logic, and that are built on top of non-supported technologies or homegrown UI toolkits, or for lower level tasks such as systemlevel verifications. Why automate functional testing processes? The pressure on today s IT organizations continues to build. Management is looking to IT to deliver new capabilities, unlock new business opportunities, and deliver competitive advantages through software. This means the addition of many more business application development projects with tighter deadlines but not always with more budget or incremental resources. At the same time, management is becoming increasingly aware of the critical links between software and revenue. Web services, online transaction processing (OLTP), and enterprise resource planning (ERP) applications are not only mission critical, they are directly tied to your company s ability to generate revenue. Today s enterprises rely on very complex computing infrastructures. A typical organization may depend on multiple applications that were built to work on different operating systems, use several different front-end clients, involve numerous business processes, and interact with many separate data sets. Testing all possible permutations of these components creates a highly complex testing situation with hundreds or thousands of testing scenarios. When software fails, the expense can be extremely high from lost sales to unproductive employees to unhappy customers, and demoralized development and QA teams. The later in the development cycle defects are found, the more expensive they are to fix. A defect identified in a production environment can be greater than 100 times more expensive to fix than the same defect identified earlier in the design phase. Automation is key to improving the speed, accuracy, and flexibility of the software testing process, enabling your company to find and fix more defects earlier. Benefits of manual testing include: Manual tests can provide fast access to testing information. Testing can be started before the application is fully stable, providing faster feedback to the development team. Manual tests provide the ability to perform simultaneous testing. Manual testing can be done simultaneously with the development and the debugging of automated scripts. Manual test scripts are easy to create. These could later be converted to automated scripts. Manual tests are easy to understand for all users, and they can be provided to business users for test validation and to developers as requirements documents or steps that lead to the discovery of bugs. 4

5 The benefits of automated functional testing The benefits of functional test automation are many and include the following: Reduce risk: By providing more comprehensive testing coverage, automated functional testing reduces the risk of production failures and increases ROI. Enable faster execution: Computers are orders of magnitude faster than humans at executing functional test scripts, so more tests can be done in less time, more applications can be tested in a given period, and more projects can be delivered on schedule. And unlike humans, computers work 24 hours a day, including nights, weekends, and holidays; they don t get bored or tired; and they don t make assumptions about what works and what does not. Here, ROI can be measured in terms of time and man-days. Facilitate greater test coverage: Automated functional testing products support the execution of test scripts across all popular browsers, operating systems, and more. Regression testing of everchanging applications and environments with automated tools is easier than with manual processes. And with integrated data-driven spreadsheet capabilities, test automation products allow your developers and QA teams to perform calculations, manipulate data sets, and quickly create multiple test iterations to expand test case coverage. With automated testing tools, any mix of transactions and any user workload can be quickly emulated. Deliver higher test accuracy and find more defects earlier: Test automation gives your developers an easier way to replicate and document software defects, helping expedite development processes while verifying correct functionality across all environments, data sets, and business processes. Provide formalized processes: The introduction of automated testing encourages your test teams to formalize their processes, resulting in higher test consistency and better documentation records. Facilitate the re-use of tests: Once tests are scripted, your developers can use, re-use, and add to the test suite as they make changes to their applications. There is no need to re-create scripts to test the same functionality for each application modification. Support ERP/CRM implementations: As more companies are implementing ERP/CRM solutions, the need to do end-to-end regression testing is becoming more frequent and more crucial. 5

6 How to identify candidates for automated testing In general, it makes sense to focus automation efforts on critical business processes, complex applications, and the use cases that comprise them (as opposed to lower-level tasks, such as systemlevel verifications). But if your enterprise has multiple software testers spending many hours per day and still has quality and functional problems, you could definitely benefit from moving to automated testing. The decision of whether or not to automate the test process should be driven by ROI considerations. In general, there will be a positive return if the application requires regression testing, requires multiple builds/patches/fixes, needs to be tested on numerous hardware or software configurations, and supports many concurrent users. In addition, if repetitive tasks such as data loading and system configuration are involved, or if the application needs to meet a specific service-level agreement (SLA), automation will certainly make economic sense. Automation does not make sense when testing the usability of a user interface (UI) or for exploratory testing or applications that are not yet mature. How to determine the ROI of automated testing The ROI for any investment can be obtained from a simple calculation: ROI = Net present value of the investment Total initial cost When it comes to automating functional testing processes, the costs are tangible but the net present value also includes many intangible factors. The best approach is to determine with as much precision as possible what the hard-dollar costs are and then compare them to the hard- and soft-dollar benefits of automating the test efforts. Hard-dollar costs to consider in an ROI calculation include: Acquisition costs The cost of initially acquiring the test automation software. Hardware costs The cost of the hardware required for functional testing. Typically, no special-purpose hardware is needed for functional testing, provided the tester has access to a standard desktop computer or workstation with an Ethernet port. Labor costs Factor in the cost of trained personnel to script test cases or build manual tests, including the costs of recruiting, hiring, paying, and retaining trained experts. Training costs Depending on which test automation product is selected, the user may need considerable training to become proficient at writing scripts for automated testing. Alternatively, companies may elect to hire professional services firms to handle the initial automated test creation. When weighing the potential rewards of automation, it is important to consider intangible benefits, such as higher morale and job satisfaction among testers, improved customer satisfaction and loyalty, and an enhanced reputation for reliable software among end users. 6

7 Clear, concise reporting: The ability to run a high volume of tests is of little benefit if the results of the tests are not easy to understand or interpret. Testing products should automatically generate reports that display all aspects of the test run and explain the results in an easy-to-read format. The reports should provide specifics about where application failures occurred and what test data was used; present application screen shots for every step to highlight any discrepancies; and provide detailed explanations of each checkpoint pass and failure. It should also be possible to share these reports across an entire QA and development team with no modifications. Evaluating automated testing software: what to look for Many vendors offer test automation products. Every solution has its own strengths and weaknesses, unique features, and market niche. Each enterprise s specific requirements will determine which option is the best fit. However, there are several key capabilities that should be included in any test automation product: Scriptless representation of automated tests: The testing product should offer a point-and-click interface for accessing and interacting with the application components under test as opposed to presenting line after line of scripting. Testers should be able to visualize each step of the business process and view and edit test cases intuitively; this will shorten the learning curve for testers and help QA teams meet urgent deadlines. Integrated data tables: One of the key benefits of automating functional testing is the ability to pump large volumes of data through the system quickly. But it is also important to be able to manipulate the data sets, perform calculations, and quickly create hundreds of test iterations and permutations with minimal effort. Your enterprise should look for products that offer integrated spreadsheets with powerful calculation capabilities. About HP functional testing solutions HP offers a complete suite of software and services for functional testing that is based on a common user experience and grows with your needs. Designed to both accelerate testing maturity and address the industry s widest array of technologies, the HP functional testing suite helps you test more, and test faster for high quality with agile delivery. Get started with highly efficient manual testing, seamlessly convert manual test sets to automated tests, leverage the unified user experience to move from GUI and API testing to complete end-to-end testing and build out a framework of reusable components at each step of the way to ease maintenance and drive ROI of your testing efforts. Only HP functional testing suite gives you the flexibility to test as you need with the simplicity of a unified testing environment. 7

8 Checklist: five keys to successful automated testing Even when there is clear evidence that automating a testing effort is economically justified, it can be difficult to determine how best to approach the transition to automated testing processes. This section outlines five fundamental principles for implementing automated software testing processes: 1. Complete a test plan document. Understanding the goals of the application to be tested is critical to the success of any testing effort. This includes thorough up-front planning to verify that test requirements are implemented correctly. HP Quality Center and Application Lifecycle Management provide the ability to manage both test cases and requirements for all applications to be tested. 2. Sub-divide the tests into test cases to be automated. It is probably impossible for your organization to automate all aspects of a test plan. Automated testing should be focused around the complex and critical business processes that map to functionality within an application as designed per the requirements. Many organizations find they can automate 60% of their total number of test cases, with some even reaching for over 90%. 3. Create automated tests. Using HP Unified Functional Testing software, users can create tests without having to do any actual scripting. HP Unified Functional Testing software captures the business process for the target application itself and allows users to create test flows that can then be saved into HP Quality Center and Application Lifecycle Management managed through the web. 4. Do data-driven tests to expand test coverage. Using the built-in data-table feature of HP Unified Functional Testing, your testers have the ability to create data-dependent tests that use specific key words stored in Microsoft Excel spreadsheets to populate fields in an application. This capability allows your testers to drive massive volumes of test data through an application. 5. Add verifications to the tests. The actual pass or fail criteria for a test are then added to the HP Unified Functional Testing software tests. The criteria include verifications of the front-end of the application, the middle tier, or the back-end database. Built-in database verification confirms the values stored in the database and verifies transaction accuracy and the data integrity of records that have been updated, deleted, or added. Summary Functional testing need not be a time-consuming or expensive proposition. By automating functional testing, your enterprise can take major steps forward in your ability to improve automated business processes. Your development and QA teams can increase both the speed and accuracy of the testing processes, and your IT department can achieve a higher ROI from software projects while reducing risk. By selecting HP Unified Functional Testing software as your test automation platform, your enterprise can take advantage of one of the most sophisticated yet easy-to-use functional testing technology solutions on the market. To modernize your functional testing practices, visit hp.com/go/functionaltesting. Get connected hp.com/go/getconnected Get the insider view on tech trends, support alerts, and HP solutions. Copyright , Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Excel are U.S. registered trademarks of Microsoft Corporation. 4AA1-1390ENW, Created May 2007; Updated November 2012, Rev. 4