Automated Testing Life cycle Testing Methodology

                Automated Testing Life cycle Testing Methodology

Phase 1: Decision to Automate Testing

The decision to automate testing represents the first phase of the ATLM. This phase covers the entire process that goes into the automated testing decision. During this phase, it's important for the test team to manage automated testing expectations and to outline the potential benefits of automated testing when implemented correctly. A test tool proposal needs to be outlined, which will be helpful in acquiring management support.

Overcoming False Expectations for Automated Testing

While it has been proven that automated testing is valuable and can produce a successful return on investment, there isn't always an immediate payback on investment. It's important to address some of the misconceptions that persist in the software industry and to manage the automated testing utopia. Following is a list of just a few of the misconceptions that need to be addressed. People often see test automation as a silver bullet; when they find that test automation requires a significant short-term investment of time and energy to achieve a long-term return on investment (ROI) of faster and cheaper regression testing (for example), the testing tool often becomes "shelfware." This is why it's important to manage expectations in order to introduce automated testing correctly into a project.

Automatic Test Plan Generation

Currently, there is no commercially available tool that can automatically create a comprehensive test plan while also supporting test design and execution.

Throughout a software test career, the test engineer can expect to witness test tool demonstrations and review an abundant amount of test tool literature. Often the test engineer will be asked to stand before one or more senior managers to give a test tool functionality overview. As always, the presenter must bear in mind the audience. In this case, the audience may represent individuals with just enough technical knowledge to make them enthusiastic about automated testing, while unaware of the complexity involved with an automated test effort. Specifically, the managers may have obtained secondhand information about automated test tools, and may have reached the wrong interpretation of the actual capability of automated test tools.

What the audience at the management presentation may be waiting to hear is that the tool you're proposing automatically develops the test plan, designs and creates the test procedures, executes all the test procedures, and analyzes the results automatically. Meanwhile, you start out the presentation by informing the group that automated test tools should be viewed as enhancements to manual testing, and that automated test tools will not automatically develop the test plan, design and create the test procedures, or execute the test procedures.

Shortly into the presentation and after several management questions, it becomes very apparent just how much of a divide exists between the reality of the test tool capabilities and the perceptions of the individuals in the audience. The term automated test tool seems to bring with it a great deal of wishful thinking that's not closely aligned with reality. An automated test tool will not replace the human factor necessary for testing a product. The proficiencies of test engineers and other quality assurance experts will still be needed to keep the test machinery running. A test tool can be viewed as an additional part of the machinery that supports the release of a good product.

One Test Tool Fits All

Currently, no single test tool exists that can be used to support all operating system environments.

Generally, a single test tool will not fulfill all the testing requirements for an organization. Consider the experience of one test engineer encountering such a situation. The test engineer was asked by a manager to find a test tool that could be used to automate the testing of all the department's applications. The department was using various technologies including mainframe computers and Sun workstations; operating systems such as Windows 3.1, Windows 95, Windows NT, and Windows 2000; programming languages such as Visual C++ and Visual Basic; other client/server technologies; and Web technologies such as DHTML, XML, ASP, and so on.

After conducting a tool evaluation, the test engineer determined that the tool of choice was not compatible with the Visual C++ third-party add-ons (in this case, Stingray grids). Another tool had to be brought in that was compatible with this specific application.

Immediate Reduction in Schedule

An automated test tool will not immediately minimize the testing schedule.

Another automated test misconception is the expectation that the use of an automated testing tool on a new project will immediately minimize the test schedule. The testing schedule will not experience the anticipated decrease at first, and an allowance for schedule increase is required when initially introducing an automated test tool. This is due to the fact that when rolling out an automated test tool, the current testing process has to be augmented or an entirely new testing process has to be developed and implemented. The entire test team—and possibly the development team—needs to become familiar with this new automated testing process (such as ATLM) and needs to follow it. Once an automatic testing process has been established and effectively implemented, the project can expect to experience gains in productivity and turnaround time that have a positive effect on schedule and cost.

Benefits of Automated Testing

The previous discussion points out and clarifies some of the false automated testing expectations that exist. The test engineer will also need to be able to elaborate on the true benefits of automated testing, when automated testing is implemented correctly and a process is followed. The test engineer must evaluate whether potential benefits fit required improvement criteria and whether the pursuit of automated testing on the project is still a logical fit, given the organizational needs. There are three significant automated test benefits (in combination with manual testing):

• Producing a reliable system.
• Improving the quality of the test effort.
• Reducing test effort and minimizing schedule.

Many return on investment case studies have been done with regard to the implementation of automated testing. One example is a research effort conducted by imbus GmbH. They conducted a test automation value study in order to collect test automation measurements with the purpose of studying the benefits of test automation versus the implementation of manual test methods. Their research determined that the breakeven point of automated testing is on average at 2.03 test runs. (T. Linz and M. Daigl, "GUI Testing Made Painless: Implementation and Results of the ESSI Project Number 24306," 1998.)

Acquiring Management Support

Whenever an organization tries to adopt a new technology, they encounter a significant effort when determining how to apply it to their needs. Even with completed training, organizations wrestle with time-consuming false starts before they become capable with the new technology. For the test team interested in implementing automated test tools, the challenge is how to best present the case for a new test automation technology and its implementation to the management team.

Test engineers need to influence management's expectations for the use of automated testing on projects. Test engineers can help to manage expectations of others in the organization by forwarding helpful information to the management staff. Bringing up test tool issues during strategy and planning meetings can also help develop better understanding of test tool capabilities for everyone involved on a project or within the organization. A test engineer can develop training material on the subject of automated testing and can advocate to management that a seminar be scheduled to conduct the training.

The first step in moving toward a decision to automate testing on a project requires that the test team adjust management understanding of the appropriate application of automated testing for the specific need at hand. For example, the test team needs to check early on whether management is cost-averse and would be unwilling to accept the estimated cost of automated test tools for a particular effort. If so, test personnel need to convince management about the potential return on investment by conducting cost/benefit analysis.

If management is willing to invest in an automated test tool, but is unable or unwilling to staff a test team with individuals having the proper software skill level or to provide for adequate test tool training, the test team needs to point out the risks involved and/or may need to reconsider a recommendation to automate test.

Management also needs to be made aware of the additional cost involved when introducing a new tool—not only for the tool purchase, but for initial schedule/cost increase, additional training costs, and for enhancing an existing testing process or implementing a new testing process.

Test automation represents highly flexible technology, which provides several ways to accomplish an objective. Use of this technology requires new ways of thinking, which only amplifies the problem of test tool implementation. Many organizations can readily come up with examples of their own experience of technology that failed to deliver on its potential because of the difficulty of overcoming the "Now what?" syndrome. The issues that organizations face when adopting automated test systems include those outlined below:

• Finding/hiring test tool experts.
• Using the correct tool for the task at hand.
• Developing and implementing an automated testing process, which includes developing automated test design and development standards.
• Analyzing various applications to determine those that are best suited for automation.
• Analyzing the test requirements to determine the ones suitable for automation.
• Training the test team on the automated testing process, automated test design, development, and execution.
• Initial increase in schedule and cost.
  
  

  Phase 2: Test Tool Acquisition

  Test tool acquisition represents the second phase of the ATLM. This phase guides the test engineer through the entire test tool evaluation and selection process, starting with confirmation of management support. Since a tool should support most of the organizations' testing requirements, whenever feasible the test engineer will need to review the system's engineering environment and other organizational needs and come up with a list of tool evaluation criteria. A review of the different types of tools available to support aspects of the entire testing lifecycle is provided in Automated Software Testing: Introduction, Management, and Performance (as part of the ATLM), enabling the reader to make an informed decision with regard to the types of tests to be performed on a particular project. The test engineer then needs to define an evaluation domain to pilot the test tool. Finally, after all those steps have been completed, the test engineer can make vendor contact to bring in the selected tool(s). Test personnel then evaluate the tool, based on sample criteria provided.
  
  

  Phase 3: Automated Testing Introduction Process

  The process of introducing automated testing to a new project team constitutes the third phase of the ATLM. This phase outlines the steps necessary to successfully introduce automated testing to a new project, which are summarized in the following sections.

  Test Process Analysis

  Test process analysis ensures that an overall test process and strategy are in place and are modified, if necessary, to allow automated testing to be introduced in a successful fashion. The test engineers define and collect test process metrics in order to allow for process improvement. Here test goals/objectives and strategies need to be defined and test process needs to be documented and communicated to the test team. In this phase, the kinds of testing applicable for the technical environment will be defined, and tests are defined that can be supported by automated tools.
  During the test process analysis, techniques are defined. Best practices are laid out, such as conducting performance testing during the unit-testing phase.
  Plans for user involvement are assessed, and test team personnel skills are analyzed against test requirements and planned test activities. Early test team participation is emphasized, supporting refinement of requirement specifications into terms that can be adequately tested while also supporting test team understanding of application requirements and design.

  Test Tool Consideration

  The test tool consideration process includes steps that investigate whether incorporation of automated test tools that have been brought into the company without a specific project in mind now would be beneficial to a specific project, given the project testing requirements, available test environment, personnel resources, user environment, platform, and product features of the application under test. Schedule is reviewed to ensure sufficient time for test tool setup and development of requirements hierarchy; potential test tools and utilities are mapped to test requirements, test tool compatibility with the application and environment is verified, and workaround solutions are investigated for incompatibility problems that surfaced during compatibility tests.
  
  

  Phase 4: Test Planning, Design, and Development

  Test planning, design, and development is the fourth phase of the ATLM. These subjects are summarized in the following sections.

  Test Planning

  The test planning stage represents the need to review long–lead-time test planning activities. During this phase, the test team identifies test procedure creation standards and guidelines; hardware, software, and network required to support test environment; test data requirements; a preliminary test schedule; performance measure requirements; a procedure to control test configuration and environment; as well as defect-tracking procedure(s) and associated tracking tool(s).
  The test plan contains the results of each preliminary phase of the structured test methodology (ATLM). The test plan will define roles and responsibilities, project test schedule, test planning and design activities, test environment preparation, test risks and contingencies, and acceptable level of thoroughness (test acceptance criteria). Test plan appendices may include test procedures, naming conventions, test procedure format standards, and a test procedure traceability matrix.
  The test environment setup is part of test planning. It represents the need to plan, track, and manage test environment setup activities, where material procurements may have long lead times. The test team needs to schedule and track environment setup activities; install test environment hardware, software, and network resources; integrate and install test environment resources; obtain/refine test databases; and develop environment setup scripts and test bed scripts.

  Test Design

  The test design component addresses the need to define the number of tests to be performed, the ways that testing will be approached (paths, functions), and the test conditions that need to be exercised. Test design standards need to be defined and followed.
  An effective test program, incorporating the automation of software testing, involves a mini-development lifecycle of its own, complete with strategy and goal planning, test requirement definition, analysis, design, and coding. Similar to software application development, test requirements must be specified before test design is constructed. Test requirements need to be clearly defined and documented, so that all project personnel will understand the basis of the test effort. Test requirements are defined within requirement statements as an outcome of test requirement analysis.
  After test requirements have been derived using the described techniques, test procedure design can begin. Test procedure design consists of the definition of logical groups of test procedures and a naming convention for the suite of test procedures. With a test procedure definition in place, each test procedure is then identified as either an automated or a manual test. During the test planning phase, the test team gets an understanding of the number of test techniques being employed and an estimate for the number of test procedures that will be required. The test team also will have an estimate of the number of test procedures that will need to be performed manually, as well as with an automated test tool.
  Much like a software development effort, the test program must be mapped out and consciously designed to ensure that test activities performed represent the most efficient and effective tests for the system under test. Test program resources are limited, yet ways of testing the system are endless. A test design is developed to portray the test effort, in order to give project and test personnel a mental framework on the boundary and scope of the test program.
  Following test analysis, the test team develops the test program design models. The first of these design models, the test program model, consists of a graphical illustration that depicts the scope of the test program. This model typically depicts the test techniques required to support the dynamic test effort and also outline static test strategies.
  Having defined a test program model, the test team constructs a test architecture, which depicts the structure of the test program and defines the way that test procedures will be organized in support of the test effort.
  The next step in the test procedure design process (see Table 1) is to identify those test procedures that stand out as being more sophisticated, and as a result are required to be defined further as part of detailed test design. These test procedures are flagged and a detailed design document is prepared in support of the more sophisticated test procedures. Following detailed test design, test data requirements are mapped against the defined test procedures. To create a repeatable, reusable process for producing test procedures, the test team needs to create a document that outlines test procedure design standards. Only when these standards are followed can the automated test program achieve real efficiency and success, by being repeatable and maintainable.
  Table 1 Test Procedure Design Process

  Step	Description
  1	Test Architecture Review. The test team reviews the test architecture in order to identify the test techniques that apply.
  2	Test Procedure Definition (Development Level). A test procedure definition is constructed at the development test level, identifying the test procedure series that applies for the various design components and test techniques.
  3	Test Procedure Definition (System Level). A test procedure definition is constructed at the system test level, identifying the test procedure series that applies for the various test techniques.
  4	Test Procedure Design Standards. Design standards are adopted and a unique naming convention is adopted that distinguishes the test procedures on the project from test procedures developed in the past or on other projects.
  5	Manual Versus Automated Tests. Test procedures will be depicted as being either performed manually or as part of an automated test.
  6	Test Procedures Flagged for Detailed Design. Test procedures that stand out as more sophisticated are flagged. These test procedures are further defined as part of detailed test design.
  7	Detailed Design. Those test procedures flagged as part of step 7 are designed in further detail within a detailed test design file or document. Test procedure detailed design may consist of pseudo-code of algorithms, preliminary test step definition, or pseudo-code of test automation programs.
  8	Test Data Mapping. Test procedure matrix is modified to reflect test data requirements for each test procedure.

  
  
  The exercise of developing the test procedure definition not only aids in test development, but helps to quantify or bound the test effort. The development of the test procedure definition involves the identification of the suite of test procedures that need to be developed and executed in support of the test effort. The design exercise involves the organization of test procedures into logical groups and the definition of a naming convention for the suite of test procedures.
  At the system level, it may be worthwhile to develop a detailed test design for sophisticated tests. These tests might involve test procedures that perform complex algorithms, consist of both manual and automated steps, and test programming scripts that are modified for use in multiple test procedures. The first step in the detailed design process is to review the test procedure definition at the system test level. This review is conducted for the purpose of identifying those test procedures that stand out as being more sophisticated and that, as a result, are required to be defined further as part of detailed test design.
  Detailed test design may take the form of test program pseudo-code, when test programming is required. The detailed design may be represented simply as a sequence of steps that need to be performed in support of a test. When programming variables and multiple data values are involved, the detailed design may reflect the programming construct of a loop supporting an iterative series of tests involving different values, together with a list or table identifying the kinds of data or ranges of data required for the test.
  Following the performance of detailed test design, test data requirements need to be mapped against the defined test procedures. Once test data requirements are outlined, the test team needs to plan the means for obtaining, generating, or developing the test data.
  The structure of the test program (test architecture) is commonly portrayed in two ways. One test procedure organization method involves the logical grouping of test procedures with the system application design components, and is referred to as a design-based test architecture. Another method represents a test technique perspective and associates test procedures with the various kinds of test techniques represented within the test program model, and is referred to as a technique-based test architecture.
  An understanding of test techniques is necessary when developing test design and the test program design models. Personnel performing testing need to be familiar with the test techniques associated with the white box and black box test-approach methods. White box test techniques are aimed at exercising software program internals; black box techniques generally compare the application under test behavior against requirements that address testing via established public interfaces such as the user interface or the published application programming interface (API).

  Test Development

  For automated tests to be reusable, repeatable, and maintainable, test development standards need to be defined and followed.
  After performing test analysis and design, the test team is now ready to perform test development.
  Keep in mind that the test design and development activities follow an iterative and incremental approach, in order to address the highest risk functionality up front. Table 2 correlates the development process phases to the test process phases. The testing processes and steps outlined in the table are strategically aligned with the development process, and the execution of these steps results in the refinement of test procedures at the same time as developers are creating the software modules. Automated and/or manual test procedures are developed during the integration test phase with the intention of reusing them during the system test phase.
  Table 2 Development/Test Relationship

  Phase	Development Process	Test Process
  Module (Unit) Development	Design module from requirements.	Perform test planning and test environment setup.
  	Code module.	Create test design and develop test data.
  	Debug module.	Write test scripts or record test scenario using module.
  	Unit test module.	Debug automated test script by running against module. Use tools that support unit testing.
  	Correct defects.	Rerun automated test script to regression test as defects are corrected.
  	Conduct performance testing.	Verify that system is scalable and will meet performance requirements.
  Integration	Build system by connecting modules. Integration-test connected modules. Review trouble reports.	Combine unit test scripts and add new scripts that demonstrate module interconnectivity. Use test tool to support automated integration testing.
  	Correct defects and update defect status.	Rerun automated test script as part of regression test, as defects are corrected.
  	Continued performance testing activities.	Verify that system is scalable and will meet performance requirements.
  System Test	Review trouble reports.	Integrate automated test scripts into system-level test procedures where possible, and develop additional system-level test procedures. Execute system test and record test results.
  	Correct defects and update defect status.	Rerun automated test script as part of regression test as defects are corrected.
  Acceptance Test	Review incident reports.	Perform subset of system test as part of demonstration of user acceptance test.
  	Correct defects.	Rerun automated test script as part of regression test as defects are corrected.

  
  
  Many preparation activities need to take place before test development can begin. A test development architecture is developed (described in the next section), which provides the test team with a clear picture of the test development preparation activities or building blocks necessary for the efficient creation of test procedures. The test team will need to tailor the sample test development architecture to reflect the priorities of their particular project. Part of these setup and preparation activities involves the need to track and manage test environment set up activities, where material procurements may have long lead times. Prior to the commencement of test development, the test team also needs to perform analysis to identify the potential for reuse of existing test procedures and scripts within the automation infrastructure (reuse library).
  The test team needs to develop test procedures according to a test procedure development/execution schedule. This schedule needs to allocate personnel resources and reflect development due dates, among other factors. The test team needs to monitor development progress and produce progress status reports. Prior to the creation of a complete suite of test procedures, the test team performs a modularity relationship analysis. The results of this analysis help to incorporate data dependencies, plan for workflow dependencies between tests, and identify common scripts that can be applied repeatedly to the test effort. As test procedures are being developed, the test team needs to ensure that configuration control is performed for the entire test bed to include test design, test scripts, and test data, as well as for each individual test procedure. The test bed needs to be baselined using a configuration management tool.
  Test development involves the development of test procedures that are maintainable, reusable, simple, and robust, which in itself can be as challenging as the development of the application under test. Test procedure development standards need to be in place supporting structured and consistent development of automated tests. Test development standards can be based on the scripting language standards of a particular test tool. For example, Rational's Robot uses SQABasic, a Visual Basic–like scripting language, and therefore the script development standards could be based on the Visual Basic development standards, outlined in a number of books on the subject.
  Usually internal development standards exist that can be followed if the organization is developing in a language similar to the tool's scripting language. The adoption or slight modification of existing development standards is generally a better approach than creating a standard from scratch. If no development standards exist within the organization for the particular tool scripting language, it's important for the test team to develop script development guidelines. Such guidelines can include directions on context independence, which addresses the particular place where a test procedure should start and where it should end. Additionally, modularity and reusability guidelines need to be addressed.
  By developing test procedures based on development guidelines, the test team creates the initial building blocks for an automation infrastructure. The automation infrastructure will eventually contain a library of common, reusable scripts. Throughout the test effort and in future releases, the test engineer can make use of the automation infrastructure to support reuse of archived test procedures, minimize duplication, and thus enhance the entire automation effort.

  Test Development Architecture

  Test team members responsible for test development need to be prepared with the proper materials. Test team personnel need to follow a test development architecture that includes, for example, a listing of the test procedures assigned to them and a listing of the outcome of automated versus manual test analysis. Also, test team personnel need to decide when to automate. At times a test team might want to avoid automating using a GUI testing tool before the interface—whether API, character UI, or GUI—is stabilized, to avoid having to reengineer the automated tests in response to non–bug-related changes. At other times, the test team might find workaround solutions when automating an unstable GUI, such as focusing automation on the known stable parts only.
  The test engineer needs to adhere to the test procedure development and execution schedule, test design information, automated test tool user manuals, and test procedure development guidelines. Armed with the proper instructions, documentation, and guidelines, test engineers will have the foundation that allows them to develop a more cohesive and structured set of test procedures. Repeating a process and repeatedly demonstrating a strong test program depends on the availability of documented processes and standard guidelines such as the test development architecture.
  Figure 2 shows an example of a graphical illustration containing the major activities to be performed as part of the test development architecture. Test development starts with test environment setup and preparation activities, discussed earlier. Once they're concluded, the test team needs to make sure that all pertinent information necessary to support development has been documented or gathered. The test team will need to tailor the sample test development architecture in Figure 2 to reflect the priorities of their particular project. Note that Figure 2 should be read from bottom to top.
  Figure 2 Building blocks of the test development architecture.

  Technical Environment

  Test procedure development needs to be preceded by several setup activities. The test development activity needs to be supported by a technical environment, which facilitates the development of test procedures. As a result, the test environment needs to be set up and ready to go. The test environment includes the technical environment, which may include facility resources as well as the hardware and software necessary to support test development and execution. The test team needs to ensure that there are enough workstations to support the entire team. The various elements of the test environment need to be outlined within the test plan, as discussed earlier.
  Environment setup activities can also include the use of an environment setup script to load test data or restore a drive image, and to calibrate the test tool to the environment. When test tool compatibility problems arise with the application under test, workaround solutions have to be identified. When developing test procedures, it's important that the schedule for developing test procedures is consistent with the test execution schedule. It's also important that the test team follow test procedure development guidelines.
  The test team must ensure that the proper test room or laboratory facilities are reserved and set up. Once the physical environment is established, the test team ensures that all necessary equipment is installed and operational. The test plan defined the required technical environment and addressed test environment planning. Within the test environment section of the test plan, the test team has already identified operational support required to install and check out the operational readiness of the technical environment. The test team needs to ensure that operational support activities have been properly scheduled and must monitor progress of these tasks.
  Specific tasks and potential issues outlined in the test plan should now have been addressed and resolved. Such issues could include network installation, network server configuration and allocated disk space, network access privileges, required desktop computer processing speed and memory, number and types of desktop computers (clients), video resolution requirements, and any additional software required to support the application, such as browser software. Automated test tools that apply should have been scheduled for installation and checkout. These tools now should be configured to support the test team and be operational within the test environment.
  The test environment setup activity includes the need to track and manage test environment setup activities, where material procurements may have long lead times. These activities include the need to schedule and track environment setup activities; install test environment hardware, software, and network resources; integrate and test-install test environment resources; obtain/refine test databases; and develop environment setup scripts and test bed scripts.
  The hardware supporting the test environment must be sufficient to ensure complete functionality of the production application. Test environment hardware needs to be sufficient to support performance analysis. In cases where the test environment utilizes hardware resources that are also supporting other development or management activities, special arrangements may be necessary during actual performance testing. During system test, the software configuration loaded within the test environment must be a complete, fully integrated release with no patches and no disabled sections. The hardware configuration supporting the test environment needs to be designed to support processing, storage, and retrieval activities, which may be performed across a local or wide area network, reflecting the target environment.
  The test environment design also needs to consider stress testing requirements. Stress and load tests may require the use of multiple workstations that will run multiple test procedures simultaneously; some automated test tools include a virtual user simulation functionality that eliminates or minimizes the need for multiple workstations.
  Test data will need to be obtained with enough lead time to support refinement and manipulation to support test requirements. Data preparation activities include the identification of conversion data requirements, the preprocessing of raw data files, loading of temporary tables—possibly in a relational database management system format, and the performance of consistency checks. Identifying conversion data requirements involves performing in-depth analysis on data elements, which includes defining data-mapping criteria, clarifying data-element definitions, confirming primary keys, and defining data-acceptable parameters.
  During test planning, the test team defined and scheduled the test environment activities. Now the team needs to track the test environment setup activities. Resources need to be identified to install hardware, software, and network resources into the test environment and integrate and test installed test environment resources. The test environment materials and the application under test need to be baselined within a configuration management tool. Additionally, test environment materials may include test data and test processes.
  The test team needs to obtain and modify test databases necessary to exercise software applications, and develop environment setup scripts and test bed scripts. The test team should perform product reviews and validation of all test source materials. The location of the test environment for each project or task should be defined within the test plan for each project. Early identification of the test site is critical to cost-effective test environment planning and development.
  
  

  Phase 5: Execution and Management of Tests

  At this stage, the test team has addressed test design and test development. Test procedures are now ready to be executed in support of exercising the application under test. Also, test environment setup planning and implementation was addressed consistent with the test requirements and guidelines provided within the test plan.
  With the test plan in hand and the test environment now operational, it's time to execute the tests defined for the test program. When executing test procedures, the test team must comply with a test procedure execution schedule, as discussed earlier. The test procedure execution schedule implements the strategy defined within the test plan. Plans for unit, integration, system, and user acceptance testing are executed. Together, these testing phases make up the steps that are required to test the system as a whole. The various steps involved during execution and management of tests are outlined below.
  • When executing test procedures, the test team needs to comply with a test procedure execution schedule. Following test execution, test outcome evaluations are performed and test result documentation is prepared.
  • Plans for unit, integration, system, and user acceptance testing are executed, which together make up the steps that are required to test the system as a whole. During the unit test phase, code profiling can be performed. Traditionally, profiling is a tuning process that determines whether an algorithm is inefficient or a function is being called too frequently. Profiling can discover instances where there is improper scaling of algorithms, instantiations, and resource utilization.
  • Integration testing is performed, which focuses on the application internals. During integration testing, units are incrementally integrated and tested together based on control flow. Since units may consist of other units, some integration testing, also called module testing, may take place during unit testing.
  • During system test, the test engineer is testing the integration of parts that comprise the entire system. A separate test team usually performs system-level tests. The test team implements the test procedure execution schedule and the system test plan.
  • The test team also performs analysis to identify particular components or functionality that are experiencing a greater relative number of problem reports. As a result of this analysis, additional test procedures and test effort may need to be assigned to the components. Test results analysis can also confirm whether executed test procedures are proving to be worthwhile in terms of identifying errors.
  • Each test team needs to perform problem-reporting operations in compliance with a defined process. The documentation and tracking of software problem reports is greatly facilitated by an automated defect-tracking tool.
  • The test team manager is responsible for ensuring that tests are executed according to schedule, and test personnel are allocated and redirected when necessary to handle problems that arise during the test effort. To perform this oversight function effectively, the test manager needs to perform test program status tracking and management reporting.
  • Test metrics provide the test manager with key indicators of the test coverage, progress, and the quality of the test effort. During white box testing, the test engineer measures the depth of testing, by collecting data relative to path coverage and test coverage. During black box testing, metrics collection focuses on the breadth of testing, to include the amount of demonstrated functionality and the amount of testing that has been performed.
    
    

    Phase 6: Test Program Review and Assessment

    Test program review and assessment activities need to be conducted throughout the testing lifecycle, to allow for continuous improvement activities. Throughout the testing lifecycle and following test execution activities, metrics need to be evaluated and final review and assessment activities need to be conducted to allow for process improvement. The various steps necessary for test program review and assessment are outlined below.
    • Following test execution, the test team needs to review the performance of the test program to determine where changes can be implemented to improve the test program performance on the next project. This test program review represents the final phase of the Automated Test Lifecycle Methodology (ATLM).
    • Throughout the test program, the test team collected various test metrics. The focus of the test program review includes an assessment of whether the application satisfies acceptance criteria and is ready to go into production. The review also includes an evaluation of earned value progress measurements and other metrics collected.
    • As part of its culture, the test team needs to adopt an ongoing iterative process of lessons learned activities. Such a program encourages test engineers to take the responsibility to raise corrective action proposals immediately, when such actions potentially have significant impact on test program performance. Throughout the entire test lifecycle, it's good practice to document and begin to evaluate lessons learned at each milestone. The metrics that are collected throughout the test lifecycle and especially during the test execution phase help pinpoint problems that need to be addressed.
    • Lessons learned, metrics evaluations, and corresponding improvement activity or corrective action need to be documented throughout the entire test process in a central repository that's easily accessible.
    • After collecting lessons learned and other metrics, and defining corrective actions, test engineers also need to assess the effectiveness of the test program to include an evaluation of the test program return on investment. Test engineers capture measures of the benefits of automation realized throughout the test lifecycle in order to support this assessment.
    • Test teams can perform their own surveys to inquire about the potential value of process and tool changes. A survey form can be used to solicit feedback on the potential use of requirement-management tools, design tools, and development tools. Surveys are helpful to identify potential misconceptions and gather positive feedback.
      
      

      Summary

      ATLM is a structured methodology geared toward ensuring successful implementation of automated testing. The ATLM approach mirrors the benefits of modern rapid application development efforts, where such efforts engage the user early in the development cycle. The end user of the software product is actively involved throughout analysis, design, development, and test of each software build, which is augmented in an incremental fashion.
      Rational Corporation lists Automated Software Testing: Introduction, Management, and Performance and the ATLM as recommended reading as part of the Rational Unified Process. Many universities and professional software test training organizations have adopted the book for their classroom. Many companies (such as Imbus GMBH, Moehrendorf, Germany) have adopted the book and ATLM as their company standard for automated software testing. Others believe that industry automated test tool vendors will soon be incorporating the book's structured methodology within their tools. Instead of performing the entire test lifecycle haphazardly, software test managers will use an ATLM-compliant test tool that automatically supports (and possibly enforces) the book's sound building-block approach to the test effort.
  
  
  
  

Read More

Generating ATU Reports - Part 1

Open Source Reporting utility (ATU Reporter) for Selenium. This will be a TestNG listener for generating customized graphical reports. Following reports can be generated by this listener --
-- Line Chart
-- Bar Chart
-- Pie Chart

Download the ATU repoter jar from:
https://drive.google.com/folderview?id=0B7rZvkq9tkwPMkJlUjJGTkJjOTA&usp=sharing

Now let us know about ATU Reports:

what details can we get from this Reports ?

For each execution of a TestNG script the following things are generated in the form of HTML pages

* An Index page -  A Start Page, you can set any Description in this page

* A Consolidated Report Page - Displays all the Runs in the form of Line and Bar Charts

* A Current Run Report Page - For each run, The Current Run page shows the number of Test cases executed in a tabular format along with the Iteration details, a Summary section and a Pie Chart

* A Test Case Report Page - This Page gives the information about a Test Case with detailed steps in a tabular format along with the screenshot, a Summary section, Execution Platform details, Author Details and provides information about Failure / Skipped / Parameters

For generating this Graphs we have used JQuery, CSS, HTML and jqPlot charting library.


* An Index page

* A Consolidated Report Page

* A Current Run Report Page

* A Test Case Report Page

Read More

Selenium WebDriver With Sikuli

Sikuli Tutorial

• Installing Eclipse Maven Plugin
• Installing Apache Maven
• Install Sikuli Script Jar in Maven Repository
• Creating Sikuli Maven Project
• Example program: Open a file in Widows Explorer
• Executing Sikuli Maven Project from Command line
• Selenium vs Sikuli
• Integrating Sikuli With Selenium WebDriver

Installing Eclipse Maven Plugin

Step #1:
Open Eclipse, Go to Help   -> Install a new Software. Click on “Add” button and add the following URL.

Click on “OK” button.
Step #2:
Check All the check boxes listed, click “Next” and install the maven plugin.
(Click on image to enlarge)

Installing Apache Maven

Step #1:
Download latest version of maven from here.
Step #2:
Extract the downloaded zip file and put it under somewhere in your machine.
Copy the bin folder path of Maven, and append the path in the environment variable.
(It requires JAVA_HOME variable in the environment variable. Please set JAVA_HOME variable in your environment)
Step #3:
Check whether maven installed correctly, Open command prompt and type “mvn -version”. It should return something like this,
(Click on image to enlarge)

It indicates Maven successfully installed in your machine.

Install Sikuli Script Jar in Maven Repository

As I mentioned in part -1, we’ve already got sikuli-script.jar, next we need to install sikuli-script.jar in maven repository.
By using the following command we can install sikuli-script.jar in maven repository.
Mvn install: install-file -Dfile=D:\Jars\Sikuli-r930\win32\Sikuli-IDE\sikuli-script.jar -DgroupId=com.test.sikuli -DartifactId=sikuli -Dversion-1.0.1 -Dpackaging=jar
(Click on image to enlarge)

Creating Sikuli Maven Project

Step #1:
Open Eclipse and create new Maven Project.
Step #2:
Add the following dependencies in your POM file.

1	<dependency>

2	<groupId>com.test.sikuli</groupId>

3	<artifactId>sikuli</artifactId>

4	<version>1.0.1</version>

5	</dependency>

6	<dependency>

7	<groupId>junit</groupId>

8	<artifactId>junit</artifactId>

9	<version>4.11</version>

10	</dependency>

(Click on image to enlarge)

Step #3:
Create a package inside src/test/java and Create a class inside the package. Now you can start writing the Sikuli script inside this class.

Sikuli Example Program: Open a file in Widows Explorer

Step #1:
Create a Sikuli Maven Project, as explained above.
Step #2:
Take screenshot of required elements and put it inside the Maven project.

– file.png
Step #3:
Create a class with name “Test1”, and Paste the following code inside the sikuli class.

1	package com.test;

2

3	import org.junit.Test;

4	import org.sikuli.script.FindFailed;

5	import org.sikuli.script.Screen;

6

7	public class Test1 {

8

9

@Test

10	public  void openFileTest() throws FindFailed, InterruptedException {

11	// TODO Auto-generated method stub

12	Screen s=new Screen();

13	s.find("file.png");

14	s.doubleClick("file.png");

15	System.out.println("File icon clicked");

16

17

}

18

}

Executing Sikuli Maven Project from Command line

Step #1:
Open Command Prompt and cd to the project directory.
Step #2:
Execute the above project from command prompt using the following command.
mvn clean test -Dtest=Test1

Selenium Vs Sikuli

Integrating Sikuli With Selenium WebDriver

Step #1:
Create a new Java Project in eclipse by clicking New -> Java project.
Step #2:

1. Right click on the Project Go to Build Path   -> Configure Build Path.
2. Switch to Libraries Tab.
3. Click on “Add External Jars” and Add Selenium library jars as well as Sikuli-scritp.jar

Step #3:
Create a package inside src/ folder and create a class under that package.
Step #4:
Take All required screenshot of web elements and save inside the project.

Step #5:
Copy the following code inside that class.

1	package com.test;

2

3	import org.openqa.selenium.WebDriver;

4	import org.openqa.selenium.firefox.FirefoxDriver;

5	import org.openqa.selenium.support.ui.WebDriverWait;

6	import org.sikuli.script.FindFailed;

7	import org.sikuli.script.Screen;

8

9	public class OnlinePainting {

10

11	public static void main(String[] args) throws FindFailed {

12	// TODO Auto-generated method stub

13

14	WebDriver driver=new FirefoxDriver();

15	WebDriverWait wait=new WebDriverWait(driver,20);

16	driver.manage().window().maximize();

17	driver.get("http://www.thecolor.com/Coloring/a-puppy-with-a-kitten.aspx");

18	Screen screen=new Screen();

19	screen.wait("1398665726055.png", 20);

20	screen.click("1398666382715.png");

21	screen.click("1398666248846.png");

22	screen.click("1398666729252.png");

23	screen.click("1398666188894.png");

24	screen.click("1398665763634.png");

25	screen.click("1398666592027.png");

26	screen.click("1398666610951.png");

27	screen.click("1398666308624.png");

28	screen.click("1398666326406.png");

29	screen.click("1398666570749.png");

30	screen.click("1398666703708.png");

31	screen.click("1398666382715.png");

32	screen.click("1398666857321.png");

33	screen.waitVanish("1398665763634.png");

34

35

}

36

}

Step #6:
Right click on the project, Select RunAs -> Java Application.
Before Execution:

After Execution:

Conclusion

• Sikuli scripts can be easily integrated with selenium WebDriver to automate flash websites.
• Sikuli can automate windows as well as all other applications.
• As it uses Visual match, we can automate almost anything, we see on the screen.
• It provides extensive support to Flash objects. i.e. we can automate adobe flash player components. (Audio player, video player)
• Sikuli scripts can be created as maven project and can be run from command prompt.
• Hence, Sikuli is most friendly, automation tool to automate challenging flash/windows applications.

Read More