Handout: Software Testing

Version: ST/Handout/1107/1.0 Date: 16-11-07

Cognizant 500 Glen Pointe Center West Teaneck, NJ 07666 Ph: 201-801-0233 www.cognizant.com

Handout – Software Testing

Introduction ...................................................................................................................................5 About this Module .........................................................................................................................5 Target Audience ...........................................................................................................................5 Module Objectives ........................................................................................................................5 Pre-requisite .................................................................................................................................5 Chapter 1: Introduction to Testing ...............................................................................................6 Learning Objectives ......................................................................................................................6 What is Software Testing..............................................................................................................6 Testing Life Cycle .........................................................................................................................6 Broad Categories of Testing .........................................................................................................7 The Testing Techniques ...............................................................................................................7 Types of Testing ...........................................................................................................................8 SUMMARY ...................................................................................................................................8 Test your Understanding ..............................................................................................................9 Chapter 2: Black Box Vs. White Box Testing ............................................................................10 Learning Objective:.....................................................................................................................10 Introduction to Black Box and White Box testing........................................................................10 Black box testing ........................................................................................................................10 Black box testing - without user involvement .............................................................................11 Black box testing - with user involvement ..................................................................................11 White Box Testing ......................................................................................................................14 Black Box (Vs) White Box...........................................................................................................18 SUMMARY .................................................................................................................................20 Test your Understanding ............................................................................................................20 Chapter 3: Other Testing Types ..................................................................................................21 Learning Objective ......................................................................................................................21 What is GUI Testing? .................................................................................................................21 Regression Testing.....................................................................................................................31 Integration Testing ......................................................................................................................38 Acceptance Testing ....................................................................................................................43 Configuration Testing & Installation Testing ...............................................................................45 Alpha testing and Beta testing ....................................................................................................48 Test your Understanding ............................................................................................................52
Page 2 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
Chapter 4: Levels of Testing .......................................................................................................53 Learning Objective ......................................................................................................................53 Unit Testing.................................................................................................................................53 Integration Testing ......................................................................................................................60 System Testing ...........................................................................................................................61 SUMMARY .................................................................................................................................64 Test your Understanding ............................................................................................................64 Chapter 5: JUnit Testing ..............................................................................................................65 Learning Objective ......................................................................................................................65 JUNIT Testing - Introduction.......................................................................................................65 Simple Test Case .......................................................................................................................65 Fixture .........................................................................................................................................66 Test Case ...................................................................................................................................67 Suite............................................................................................................................................67 TestRunner .................................................................................................................................68 Chapter 6: Testing Artifacts ........................................................................................................70 Learning Objective ......................................................................................................................70 Test Strategy and Test Plan .......................................................................................................70 Test Plan.....................................................................................................................................75 Test Case .................................................................................................................................100 SUMMARY ...............................................................................................................................103 Test your Understanding ..........................................................................................................103 Chapter 7: Defect Management .................................................................................................104 Learning Objective ....................................................................................................................104 What is a Defect? .....................................................................................................................104 Defect Lifecycle ........................................................................................................................105 Defect Reporting and Tracking .................................................................................................105 SUMMARY ...............................................................................................................................107 Test your Understanding ..........................................................................................................108 Chapter 8: Automation ...............................................................................................................109 Learning Objective ....................................................................................................................109 What is Automation? ................................................................................................................109 Automation Benefits .................................................................................................................109 Automation Life Cycle...............................................................................................................111 Test Environment Setup ...........................................................................................................113 Other Phases in Automation.....................................................................................................116
Page 3 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

.................................140 Supported environments ................................................................................Handout – Software Testing Automation Methods...........................................................................................163 SUMMARY .............167 SUMMARY .............................................................................................................................126 Rational Suite of tools.................................................................................................................................................................................................................................................................................................................126 Rational Administrator ............................................................................................................................125 Chapter 9: Sample Test Automation Tool ............................167 What is a Test Case Point (TCP)? ..............126 Learning Objective ......................................................................................................................................................................................................... All Rights Reserved C3: Protected .........................142 SUMMARY .......................................166 Chapter 11: Test Case Point .............144 Performance Testing Requirements ................................................................144 Learning Objective ............................174 WEBSITES .............................................................................................167 Learning Objective .................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................130 Rational Test Manager ....................................................................172 Test your Understanding ..........................................................................................................................................................................................................................175 Page 4 ©Copyright 2007.......................................................................167 Test Case Point Analysis....................................................................................................................126 Sample Test Automation Tool ................................................................................................ Cognizant Technology Solutions.....174 BOOKS .............................127 Rational Robot .................................................................................................174 STUDENT NOTES: ..................................................................................................................146 Performance Testing Process .........................................................................154 Volume and Stress Testing ...............................................172 REFERENCES .......................................................147 Performance Testing Tools ....................................................................................................144 What is Performance testing? ..........118 SUMMARY ........................................................................................................................................................................................143 Chapter 10: Performance Testing ................................................................................................................................................................117 Automation tool comparison ...................................................................................................

the student will be able to: Explain Software Testing List the types of testing Explain Test Strategy Describe Test Plan Describe Test Design Describe Test Cases Describe Test Data Explain Test Execution Perform Defect reporting and analyzing the defects List Test Automation advantages and disadvantages Work with Winrunner Describe Performance Testing Work with Loadrunner Too Work with Test Director Pre-requisite This module does not require any prerequisite Page 5 ©Copyright 2007.Handout – Software Testing Introduction About this Module This module provides you with a brief description of the module. suggested prerequisites and module objectives. All Rights Reserved C3: Protected . Cognizant Technology Solutions. Target Audience Entry Level Trainees Module Objectives After completing this module. audience.

Involving software testing in all phases of the software Page 6 ©Copyright 2007. stability. Refer to the ISO standard ISO 9126 for a more complete list of attributes and criteria. not prove that there are none. but effective testing of complex products is essentially a process of investigation. the scope of testing can be tailored. There are many approaches to software testing. Although most of the intellectual processes of testing are nearly identical to that of review or inspection. According to the respective projects. not merely a matter of creating and following rote procedure. completeness and quality of developed computer software. maintainability and usability. Cognizant Technology Solutions. Software Testing has been accepted as a separate discipline to the extent that there is a separate life cycle for the testing activity. One definition of testing is "the process of questioning a product in order to evaluate it. All Rights Reserved C3: Protected . and the product answers with its behavior in reaction to the probing of the tester. as this can only be done by formal verification (and only when there is no mistake in the formal verification process). Testing Life Cycle Every testing project has to follow the waterfall model of the testing process. but the process mentioned above is common to any testing activity. the word testing is connoted to mean the dynamic analysis of the product-. portability." where the "questions" are things the tester tries to do with the product.putting the product through its paces. testing can never establish the correctness of computer software. The quality of the application can and normally does vary widely from system to system but some of the common quality attributes include reliability. It can only find defects.Handout – Software Testing Chapter 1: Introduction to Testing Learning Objectives After completing this topic you will be able to: Explain the need for Software testing What is Software Testing Software testing is a process used to identify the correctness. Actually.

Handout – Software Testing development life cycle has become a necessity as part of the software quality assurance process. This type of testing is called Static Testing. The V-Model of the Software Testing Life Cycle along with the Software Development Life cycle given below indicates the various phases or levels of testing. user documentation. there needs to be testing done on Software Testing every phase. Static Testing Dynamic Testing The kind of verification we do on the software work products before the process of compilation and creation of an executable is more of Requirement review. Black-Box testing technique: This technique is used for testing based solely on analysis of requirements (specification. design review.). there are two widely used testing techniques. we see that there are two categories of testing activities that can be done on software. code. Also known as functional testing. code review. White-Box testing technique: This technique us used for testing based on analysis of internal logic (design. Broad Categories of Testing Based on the V-Model mentioned above. The above said testing types are performed based on the following testing techniques. etc. namely. it is called Dynamic Testing. walkthrough and audits. The Testing Techniques To perform these types of testing. These topics will be elaborated in the coming chapters Page 7 ©Copyright 2007. When we test the software by executing and comparing the actual & expected results. Cognizant Technology Solutions. Also known as Structural testing. All Rights Reserved C3: Protected . Right from the Requirements study till the implementation.) (But expected results still come requirements).

Performance Testing: To evaluate the time taken or response time of the system to perform it’s required functions in comparison Stress Testing: To evaluate a system beyond the limits of the specified requirements or system resources (such as disk space.e. Done to verify if it satisfies its functional specification or its intended design structure. processor utilization) to ensure the system do not break unexpectedly Load Testing: Load Testing. User Acceptance testing etc. System Testing: Testing the software for the required specifications on the intended hardware Acceptance Testing: Formal testing conducted to determine whether or not a system satisfies its acceptance criteria. verifies that a web site can handle a particular number of concurrent users while maintaining acceptable response times Alpha Testing: Testing of a software product or system conducted at the developer’s site by the Customer Beta Testing: Testing conducted at one or more customer sites by the end user of a delivered software product system. Let us see a brief definition on the widely employed types of testing. which enables a customer to determine whether to accept the system or not.Handout – Software Testing Types of Testing From the V-model. a subset of stress testing. Unit Testing: The testing done to a unit or to a smallest piece of software. All Rights Reserved C3: Protected . memory. System testing. integrated) to form higher-level elements Regression Testing: Selective re-testing of a system to verify the modification (bug fixes) have not caused unintended effects and that system still complies with its specified requirements. Cognizant Technology Solutions. Integration Testing: Testing which takes place as sub elements are combined (i. Integration testing.. SUMMARY “Testing is the process of executing a program with the intent of finding errors” Evolution of Software Testing The Testing process and lifecycle Broad categories of testing Widely employed Types of Testing The Testing Techniques Page 8 ©Copyright 2007. namely. Unit testing. we see that are various levels or phases of testing.

Cognizant Technology Solutions.Handout – Software Testing Test your Understanding 1. The primary objective of testing is a) To show that the program works b) To provide a detailed indication of quality c) To find errors d) To protect the end –user Answers: 1) c Page 9 ©Copyright 2007. All Rights Reserved C3: Protected .

While black-box and white-box are terms that are still in popular use. For this reason. It is usually described as focusing on testing functional requirements. test groups are often used. Synonyms for white-box include: structural. there are two types of black box test that involve users. Though centered around the knowledge of user requirements. For example. it hasn't proven useful to use a single test design method. so it doesn't explicitly use knowledge of the internal structure. glass-box and clear-box. functional. and how to build and maintain test data. and benchmarks. For this testing. Synonyms for black-box include: behavioral. and it focuses specifically on using internal knowledge of the software to guide the selection of test data. opaque-box. test coverage. Some call this "graybox" or "translucent-box" test design. many people prefer the terms "behavioral" and "structural". Behavioral test design is slightly different from black-box test design because the use of internal knowledge isn't strictly forbidden. Additionally. In practice. In the following the most important aspects of these black box tests will be described briefly. no other knowledge of the program is necessary. volume tests. the tester and the programmer can be independent of one another. White-box test design allows one to peek inside the "box". White Box Testing Learning Objective: After completing this chapter. There are 2 primary methods by which tests can be designed and they are: Black box White box Black-box test design treats the system as a literal "black-box". the tester would only know the "legal" inputs and what the expected outputs should be. stress tests. It is because of this that black box testing can be considered testing with respect to the specifications. avoiding programmer bias toward his own work. black box tests do not necessarily involve the participation of users. recovery testing. One has to use a mixture of different methods so that they aren't hindered by the limitations of a particular one. Page 10 ©Copyright 2007. It is used to detect errors by means of execution-oriented test cases. Cognizant Technology Solutions. All Rights Reserved C3: Protected . how to develop and document test cases. but it's still discouraged. but not how the program actually arrives at those outputs. you will be able to: Explain the methods of testing Introduction to Black Box and White Box testing Test Design refers to understanding the sources of test cases. but others wish we'd stop talking about boxes altogether!!! Black box testing Black Box Testing is testing without knowledge of the internal workings of the item being tested. Among the most important black box tests that do not involve users are functionality testing. when black box testing is applied to software engineering. field and laboratory tests. and closedbox.e. i.Handout – Software Testing Chapter 2: Black Box Vs.

Whereas for most software engineers benchmark tests are concerned with the quantitative measurement of specific operations. The notion of benchmark tests involves the testing of program efficiency. A volume test can uncover problems that are related to the efficiency of a system.e. Moreover. a consumption of too much memory space. In short it involves putting the system into its intended use by its envisaged type of user. recovery testing is very important. what is specified in the requirements.without user involvement The so-called ``functionality testing'' is central to most testing exercises. One is the testing of each program feature or function in sequence. or. i. e. how the technical integration of the system works.e. sending e-mails. The other is to test module by module. Cognizant Technology Solutions. During a stress test. E.with user involvement For tests involving users.g. Apart from general usability-related aspects. field tests are particularly useful for assessing the interoperability of the software system. i. benchmark tests only denote operations that are independent of personal variables. some also consider user tests that compare the efficiency of different software systems as benchmark tests. each function where it is called first. In the context of this document.g. Black box testing . The objective of volume tests is to find the limitations of the software by processing a huge amount of data. however. In field tests users are observed while using the software system at their normal working place. performing a standardised task. A scenario test is a test case which aims at a realistic user background for the evaluation of software as it was defined and performed It is an instance of black box testing where the major objective is to assess the suitability of a software product for every-day routines. incorrect buffer sizes. Particularly in the NLP environment Page 11 ©Copyright 2007. Does the system provide possibilities to recover all of the data or part of it? How much can be recovered and how? Is the recovered data still correct and consistent? Particularly for software that needs high reliability standards. There are different approaches to functionality testing. The aim of recovery testing is to make sure to which extent data can be recovered after a system breakdown. All Rights Reserved C3: Protected . i. field tests are the only real means to elucidate problems of the organizational integration of the software system into existing procedures. the system has to process a huge amount of data or perform many function calls within a short period of time. to modify a term bank via different terminals simultaneously). The term ``scenario'' has entered software evaluation in the early 1990s . in the NLP area. one may find practical test reports that distinguish roughly between field and laboratory tests.e.Handout – Software Testing Black box testing . methodological considerations are rare in SE literature. Rather. The efficiency of a piece of software strongly depends on the hardware environment and therefore benchmark tests always consider the soft/hardware combination. In the following only a rough description of field and laboratory tests will be given. or only show that an error message would be needed telling the user that the system cannot process the given amount of data.g. Its primary objective is to assess whether the program does what it is supposed to do. A typical example could be to perform the same function from all workstations connected in a LAN within a short period of time (e. Scenario Tests.

state. Special techniques as appropriate--syntax. loop. individual translators are not too motivated to change their working habits. especially with real time systems Crash testing should be performed to see what it takes to bring the system down Test monitoring tools should be used whenever possible to track which tests have already been performed and the outputs of these tests to avoid repetition and to aid in the software maintenance Other functional testing techniques include: transaction testing. Finite state machine models can be used as a guide to design functional tests According to Beizer the following is a general order by which tests should be designed: o o o o o o Clean tests against requirements. Laboratory tests are mostly performed to assess the general usability of the system. as needed. Black box testing Methods Graph-based Testing Methods Black-box methods based on the nature of the relationships (links) among the program objects (nodes). Testing Strategies/Techniques Black box testing should make use of randomly generated inputs (only a test range should be specified by the tester). Additional tests for data-flow coverage as needed. All Rights Reserved C3: Protected . Due to the high laboratory equipment costs laboratory tests are mostly only performed at big software houses such as IBM or Microsoft. where the major implementation problem is not the technical environment. test cases are designed to traverse the entire graph Transaction flow testing (nodes represent steps in some transaction and links represent logical connections between steps that need to be validated) Page 12 ©Copyright 2007.Handout – Software Testing this problem has frequently been underestimated. data collection and analysis are easier than for field tests. and state testing. Additional structural tests for branch coverage. syntax testing. logic testing. to eliminate any guess work by the tester as to the methods of the function Data outside of the specified input range should be tested to check the robustness of the program Boundary cases should be tested (top and bottom of specified range) to make sure the highest and lowest allowable inputs produce proper output The number zero should be tested when numerical data is to be input Stress testing should be performed (try to overload the program with inputs to see where it reaches its maximum capacity). Cognizant Technology Solutions. domain testing. Domain tests not covered by the above. Any dirty tests not covered by the above. but the fact that many clients still submit their orders as print-out. A typical example of the organizational problem of implementing a translation memory is the language service of a big automobile manufacturer. that neither source texts nor target texts are properly organised and stored and. Since laboratory tests provide testers with many technical possibilities. last but not least. etc.

Cognizant Technology Solutions. size limitations). one valid and one invalid equivalence class is defined If an input condition is Boolean. link weights are required execution times) Equivalence Partitioning Black-box technique that divides the input domain into classes of data from which test cases can be derived An ideal test case uncovers a class of errors that might require many arbitrary test cases to be executed before a general error is observed Equivalence class guidelines: o o o o o If input condition specifies a range. test cases should be designed to produce the minimum and maxim output reports If internal program data structures have boundaries (e. All Rights Reserved C3: Protected . be certain to test the boundaries Comparison Testing Black-box testing for safety critical systems in which independently developed implementations of redundant systems are tested for conformance to specifications Often equivalence class partitioning is used to develop a common set of test cases for each implementation Orthogonal Array Testing Black-box technique that enables the design of a reasonably small set of test cases that provide maximum test coverage Focus is on categories of faulty logic likely to be present in the software component (without examining the code) Page 13 ©Copyright 2007.Handout – Software Testing Finite state modeling (nodes represent user observable states of the software and links represent transitions between states) Data flow modeling (nodes are data objects and links are transformations from one data object to another) Timing modeling (nodes are program objects and links are sequential connections between these objects.g. values just above and just below a and b If an input condition specifies and number of values. as well as values just above and just below the minimum and maximum values Apply guidelines 1 and 2 to output conditions. one valid and one invalid equivalence class is defined Boundary Value Analysis Black-box technique that focuses on the boundaries of the input domain rather than its center BVA guidelines: If input condition specifies a range bounded by values a and b. test cases should exercise the minimum and maximum numbers. one valid and two invalid equivalence classes are defined If an input condition specifies a member of a set. one valid and two invalid equivalence classes are defined If an input condition requires a specific value. test cases should include a and b.

test cases are hard to design There may be unnecessary repetition of test inputs if the tester is not informed of test cases the programmer has already tried May leave many program paths untested Cannot be directed toward specific segments of code which may be very complex (and therefore more error prone) Most testing related research has been directed toward glass box testing White Box Testing Software testing approaches that examine the program structure and derive test data from the program logic. including specific programming languages Tester and programmer are independent of each other Tests are done from a user's point of view Will help to expose any ambiguities or inconsistencies in the specifications Test cases can be designed as soon as the specifications are complete Disadvantages of Black Box Testing Only a small number of possible inputs can actually be tested. to test every possible input stream would take nearly forever Without clear and concise specifications. Structural testing is sometimes referred to as clear-box testing since white boxes are considered opaque and do not really permit visibility into the code. Cognizant Technology Solutions. Synonyms for white box testing Glass Box testing Structural testing Clear Box testing Page 14 ©Copyright 2007. All Rights Reserved C3: Protected .Handout – Software Testing Priorities for assessing tests using an orthogonal array Detect and isolate all single mode faults Detect all double mode faults Multimode faults Specialized Testing Graphical user interfaces Client/server architectures Documentation and help facilities Real-time systems o o o o Task testing (test each time dependent task independently) Behavioral testing (simulate system response to external events) Inter task testing (check communications errors among tasks) System testing (check interaction of integrated system software and hardware) Advantages of Black Box Testing More effective on larger units of code than glass box testing Tester needs no knowledge of implementation.

1 Code Coverage Analysis 1. Perform complete coverage at the component level. Provide a complementary function to black box testing. results verification and documentation capabilities. Practices: This section outlines some of the general practices comprising white-box testing process.1. Page 15 ©Copyright 2007. In general. drivers and test object libraries. 1.1 Basis Path Testing A testing mechanism proposed by McCabe whose aim is to derive a logical complexity measure of a procedural design and use this as a guide for defining a basic set of execution paths. white-box testing practices have the following considerations: The allocation of resources to perform class and method analysis and to document and review the same. naming conventions and libraries. document and manage a test history library. The means to develop or acquire tool support for automation of capture/replay/compare. Improve quality by optimizing performance. Cognizant Technology Solutions. Developing a test harness made up of stubs. Development and use of standard procedures. All Rights Reserved C3: Protected .Handout – Software Testing Open Box Testing Types of White Box testing A typical rollout of a product is shown in figure 1 below. These are test cases that exercise basic set will execute every statement at least once. Allocation of resources to design. The purpose of white box testing Initiate a strategic initiative to build quality throughout the life cycle of a software product or service. test suite execution. Establishment and maintenance of regression test suites and procedures.1 Flow Graph Notation A notation for representing control flow similar to flow charts and UML activity diagrams.

2. 1. Cognizant Technology Solutions. possibly proceeded by a NOT operator. Examples: Note that unstructured loops are not to be tested rather. Compound condition: composed of two or more simple conditions. Can define loops as simple. 3).2 Control Structure testing 1. Boolean expression: Condition without Relational expressions. 1. nested. 2).1 Conditions Testing Condition testing aims to exercise all logical conditions in a program module.2 Cyclomatic Complexity The cyclomatic complexity gives a quantitative measure of 4the logical complexity. Simple condition: Boolean variable or relational expression.1. This value gives the number of independent paths in the basis set.3 Loop Testing Loops fundamental to many algorithms. An independent path is any path through a program that introduces at least one new set of processing statements or a new condition (i. Boolean operators and parentheses. concatenated.. and unstructured. Cyclomatic complexity provides upper bound for number of tests required to guarantee coverage of all program statements. 1.2 Data Flow Testing Selects test paths according to the location of definitions and use of variables. Page 16 ©Copyright 2007.Handout – Software Testing 1.2. All Rights Reserved C3: Protected .e. where E1 and E2 are arithmetic expressions. and an upper bound for the number of tests to ensure that each statement is executed at least once. Relational expression: (E1 op E2). 4). they are redesigned. a new edge). They may define: 1).2.

4 Error Handling Exception and error handling is checked thoroughly are simulating partial and complete fail-over by operating on error causing test vectors.html] may also be used to perform this function.htm] are used to perform this function.research. may be validated to ensure that ACID (Atomicity. Isolation. Durability). All Rights Reserved C3: Protected . Advantages of White Box Testing Forces test developer to reason carefully about implementation Approximate the partitioning done by execution equivalence Reveals errors in "hidden" code Beneficent side-effects Disadvantages of White Box Testing Expensive Cases omitted in the code could be missed out. the code specification is expressed unambiguously using a formal language that describes the code's implicit contracts. local or distributed.ibm. 5 Transactions Systems that employ transaction. notification and logging are checked against references to validate program design.parasoft. Cognizant Technology Solutions. Proper error recovery.com/products/jtract/index. Basically. These include the use of Microsoft Java Profiler API and Sun’s profiling tools that are bundled with the JDK.com/journal/sj/391/kazi. These contracts specify such requirements as: Conditions that the client must meet before a method is invoked. It identifies routines that are consuming the majority of the CPU time so that problems may be tracked down to improve performance. Third party tools such as JaViz [http://www. 3 Profiling Profiling provides a framework for analyzing Java code performance for speed and heap memory use. Page 17 ©Copyright 2007.Handout – Software Testing 2 Design by Contract (DbC) DbC is a formal way of using comments to incorporate specification information into the code itself. Transactions are checked thoroughly for partial/complete commits and rollbacks encompassing databases and other XA compliant transaction processors. Conditions that a method must meet after it executes. Assertions that a method must satisfy at specific points of its execution Tools that check DbC contracts at runtime such as Jcontract [http://www. Consistency. Each of the individual parameters is tested individually against a reference data set.

and dials on the outside. You must test it without opening it up. Black box software testing is doing the same thing. Boundary testing and other attack-based techniques are targeted at common coding errors. Thus. Code-based testing is often called “white box” because it makes sure that all the code (the statements. Black box testing begins with a metaphor. People: Who do the testing? Some people know how software works (developers) and others just use it (users). Effective security testing also requires a detailed understanding of the code and the system architecture. paths. or decisions) is exercised. consider the Five-Fold Testing System. These terms are commonly used. and you can’t see beyond its surface. Developer testing is called “white box” testing. Imagine you’re testing an electronics system. this is called white box testing. these techniques might be Page 18 ©Copyright 2007. By analogy. An opposite test approach would be to open up the electronics system. Cognizant Technology Solutions. yet everyone seems to have a different idea of what they mean. however. To help understand the different ways that software testing can be divided between black box and white box techniques. These are the two most commonly used coverage criteria. Risks: Why are you testing? Sometimes testing is targeted at particular risks. but with software. Accordingly. The actual meaning of the metaphor. any testing by users or other non-developers is sometimes called “black box” testing. All Rights Reserved C3: Protected . Requirements-based testing could be called “black box” because it makes sure that all the customer requirements have been verified. This is black box testing. “black box” testing becomes another name for system testing. switches. Both are supported by extensive literature and commercial tools. It lays out five dimensions that can be used for examining testing: People (who do the testing) Coverage (what gets tested) Risks (why you are testing) Activities (how you are testing) Evaluation (how you know you’ve found a bug) Let’s use this system to understand and clarify the characteristics of black box and white box testing.Handout – Software Testing Black Box (Vs) White Box An easy way to start up a debate in a software testing forum is to ask the difference between black box and white box testing. apply probes internally and maybe even disassemble parts of it. You have to see if it works just by flipping switches (inputs) and seeing what happens to the lights and dials (outputs). depends on how you define the boundary of the box and what kind of access the “blackness” is blocking. This is one way to think about coverage. And testing the units inside the box becomes white box testing. Another is to contrast testing that aims to cover all the requirements with testing that aims to cover all the code. It’s housed in a black box with lights. see how the circuits are wired. Coverage: What is tested? If we draw the box around the system as a whole. The distinction here is based on what the person knows or can understand.

and maps code inspection (static testing) with white box testing. The advice given is to start test planning with a black box test approach as soon as the specification is available. Assertions are another technique for helping to make problems more visible. White box testing is much more expensive than black box testing. helping with diagnosis. All Rights Reserved C3: Protected . Another set of risks concerns whether the software will actually provide value to users. since they use code instrumentation to make the internal workings of the software more visible. Certain test techniques seek to make these kinds of problems more visible.” Activities: How do you test? A common distinction is made between behavioral test design. In order to fully test a software product both black and white box testing are required. White box testing is testing against the implementation and will discover faults of commission. These contrast with black box techniques that simply look at the official outputs of a program. The paths should then be checked against the black box test plan and any additional required test runs determined and applied. To conclude. Evaluation: How do you know if you’ve found a bug? There are certain kinds of software faults that don’t always lead to obvious failures. These are two design approaches. Cognizant Technology Solutions. with the production of flowgraphs and determination of paths. Black box testing is concerned only with testing the specification. They may be masked by fault tolerance or simply luck. Page 19 ©Copyright 2007. which defines tests based on functional requirements. the metaphor maps test execution (dynamic testing) with black box testing. this is probably the most commonly cited definition for black box and white box testing. and structural test design. Some tool vendors refer to code-coverage tools as white box tools. apart from the above described analytical methods of both glass and black box testing. The consequences of test failure at this stage may be very expensive. it cannot guarantee that the complete specification has been implemented. indicating that part of the implementation is faulty. which defines tests based on the code itself. Memory leaks and wild pointers are examples. and tools that facilitate applying inputs and capturing inputs—most notably GUI capture replay tools—as black box tools. Usability testing focuses on this risk. All of these techniques could be considered white box test techniques. Thus black box testing is testing against the specification and will discover faults of omission. it is often called “black box. Testing is then categorized based on the types of tools used. White box testing is concerned only with testing the software product. In this case.” Indeed. and could be termed “black box. there are further constructive means to guarantee high quality software end products. Related techniques capture code history and stack information when faults occur. A failure of a white box test may result in a change which requires all black box testing to be repeated and the redetermination of the white box paths. It requires the source code to be produced before the tests can be planned and is much more laborious in the determination of suitable input data and the determination if the software is or is not correct. it cannot guarantee that all parts of the implementation have been tested. Another activity-based distinction contrasts dynamic test execution with formal code inspection.” while structural testing—based on the code internals—is called “white box.Handout – Software Testing classified as “white box”. indicating that part of the specification has not been fulfilled. White box planning should commence as soon as all black box tests have been successfully passed. We could also focus on the tools used. Since behavioral testing is based on external functional definition.

Handout – Software Testing Among the most important constructive means are the usage of object-oriented programming tools. structural testing. on the other hand. White box testing. Synonyms for black-box include: behavioral. All Rights Reserved C3: Protected . unit or code-coverage testing (coverage). white-box test case design requires that you have a) Source code b) An operational program c) A detailed procedural design d) The program architecture Answers: 1). Black-box test design treats the system as a literal "black-box". opaque-box. and last but not least the involvement of users in both software development and testing procedures SUMMARY Black box testing can sometimes describe user-based testing (people). usability testing (risk). can sometimes describe developer-based testing (people). It is used to detect errors by means of execution-oriented test cases. rapid prototyping. assertions. and logs (evaluation). c Page 20 ©Copyright 2007. so it doesn't explicitly use knowledge of the internal structure. Equivalence partitioning is a black-box testing method that a) Looks for equivalent data values in the program b) Looks for classes of output c) Focuses on output errors d) Defines classes of input 2. glass-box and clear-box. d 2). inspection or code-coverage automation (activities). Synonyms for white-box include: structural. the integration of CASE tools. and closed-box White-box test design allows one to peek inside the "box". boundary or security testing (risks). It is usually described as focusing on testing functional requirements. and it focuses specifically on using internal knowledge of the software to guide the selection of test data. or behavioral testing or capture replay automation (activities). functional. At a minimum. system or requirements-based testing (coverage). or testing based on probes. Test your Understanding 1. Cognizant Technology Solutions.

English and clarity. Tab order should be left to right. then some enquiry in progress message should be displayed. Check if the title of the window make sense.) F1 key should work the same. This should not be allowed . Page 21 ©Copyright 2007. The following is a set of guidelines to ensure effective GUI Testing and can be used even as a checklist while testing a product / application. and Up to Down within a group box on the screen.indicated by dotted box. No Login is necessary. The end user should be comfortable while using all the components on screen and the components should also perform their functionality with utmost clarity. Closing the application should result in an "Are you Sure" message box Attempt to start application twice. version number. If the screen has a Control menu. Window should return to an icon on the bottom of the screen. All controls should get focus . If there is no hour glass. The Loading message should show the application name. These should be checked for spelling. Cognizant Technology Solutions.especially the error messages. or cursor. It should not be possible to select them with either the mouse or by using TAB.e. It is absolutely essential that any application has to be user-friendly. The window caption for every application should have the name of the application and the window name .Check for spelling. GUI Testing can refer to just ensuring that the look-and-feel of the application is acceptable to the user. Check all text on window for Spelling/Tense and Grammar. then the hour glass should be displayed. click it. Try this for every grayed control. The main window of the application should have the same caption as the caption of the icon in Program Manager. Try to start the application twice as it is loading. Hence it becomes very essential to test the GUI components of any application. you will be able to Explain the methods of testing What is GUI Testing? GUI is the abbreviation for Graphic User Interface. then use all ungrayed options. If a field is disabled (grayed) then it should not get focus. or it can refer to testing the functionality of each and every component involved. All screens should have a Help button (i. especially on the top of the screen. Use TAB to move focus around the Window. clarity and non-updateable etc. On each window.Windows Compliance Testing Application Start Application by Double Clicking on its ICON. Section 1 . Use SHIFT+TAB to move focus backwards.Handout – Software Testing Chapter 3: Other Testing Types Learning Objective After completing this chapter. if the application is busy. Double Click the Icon to return the Window to its original size. The text in the Micro Help line should change . This icon should correspond to the Original Icon under Program Manager. All Rights Reserved C3: Protected .you should be returned to main window. If Window has a Minimize Button. and a bigger pictorial representation of the icon. Tabbing to an entry field with text in it should highlight the entire text in the field.

All Rights Reserved C3: Protected . Double Click should select all text in box. SHIFT and Arrow should Select Characters. Select with mouse by clicking. All Buttons except for OK and Cancel should have a letter Access to them. If pressing the Command button results in uncorrectable data e. List boxes are always white background with black text whether they are disabled or not. try strange characters like + . All others are gray. SPACE should do the same. Click each button once with the mouse . Enter invalid characters . which is at the top or the bottom of the list box. Tab to another type of control (not a command button). You should not be able to type text in the box. So should Up and Down. If there is a Cancel Button on the screen. Pressing Return in ANY no command button control should activate it. Drop down with the item selected should be display the list with the selected item on the top. then pressing <Esc> should activate it. double-clicking is not essential. Check Boxes Clicking with the mouse on the box.). This is indicated by a letter underlined in the button text. Command Buttons If Command Button leads to another Screen. everything can be done using both the mouse and the keyboard. there should be a message phrased positively with Yes/No answers where Yes results in the completion of the action. Make sure only one space appears. Spacing should be compatible with the existing windows spacing (word etc. Refer to previous page. Cognizant Technology Solutions. and if the user can enter or change details on the other screen then the Text on the button should be followed by three dots. Selection should also be possible with mouse. closing an action step.Letters in amount fields.This should activate The above are VERY IMPORTANT.Handout – Software Testing Never updateable fields should be displayed with black text on a gray background with a black label. Option (Radio Buttons) Left and Right arrows should move 'ON' Selection.Press SPACE This should activate Tab to each button . shouldn't have a blank line at the bottom.* etc. Page 22 ©Copyright 2007. Pressing ALT+Letter should activate the button. In a field that may or may not be updateable. followed by a colon tight to it.Press RETURN . All text should be left justified. One button on the screen should be default (indicated by a thick black border).g. Enter text into Box Try to overflow the text by typing to many characters – should be stopped Check the field width with capitals W. the label text and contents changes from black to gray depending on the current status. or on the text should SET/UNSET the box. in All fields. In general. . Pressing ‘Ctrl . This List may be scrollable. Cursor should change from arrow to Insert Bar. All tab buttons should have a distinct letter. Text Boxes Move the Mouse Cursor over all Enterable Text Boxes. Pressing a letter should bring you to the first item in the list with that start with that letter.This should activate Tab to each button . In general. Drop Down List Boxes Pressing the Arrow should give list of options. Make sure there is no duplication.F4’ should open/drop down the list box. If it doesn't then the text in the box should be gray or non-updateable. and should be done for EVERY command Button. Items should be in alphabetical order with the exception of blank/none.

Pressing a letter should take you to the first item in the list starting with that letter. make sure all the data can be seen in the box. Cognizant Technology Solutions.Screen Validation Checklist Aesthetic Conditions: Is the general screen background of the correct color? Are the field prompts of the correct color? Are the field backgrounds of the correct color? In read-only mode. which have failed validation tests? Have any fields got multiple validation rules and if so are all rules being applied? If the user enters an invalid value and clicks on the OK button (i. Is all the micro-help text spelt correctly on this screen? Is all the error message text spelt correctly on this screen? Is all user input captured in UPPER case or lowercase consistently? Where the database requires a value (other than null) then this should be defaulted into fields. Assure that all dialog boxes have a consistent look and feel. Force the scroll bar to appear. or using the Up and Down Arrow keys. The user must either enter an alternative valid value or leave the default value intact. are the field backgrounds of the correct color? Are all the screen prompts specified in the correct screen font? Is the text in all fields specified in the correct screen font? Are all the field prompts aligned perfectly on the screen? Are all the field edit boxes aligned perfectly on the screen? Are all group boxes aligned correctly on the screen? Should the screen be resizable? Should the screen be allowed to minimize? Are all the field prompts spelt correctly? Are all character or alphanumeric fields left justified? This is the default unless otherwise specified. are the field prompts of the correct color? In read-only mode. does not TAB off the field) is the invalid entry identified and highlighted correctly with an error message? Page 23 ©Copyright 2007. Section 2 . Clicking Arrow should allow user to choose from list List Boxes Should allow a single selection to be chosen. If there is a 'View' or 'Open' button besides the list box then double clicking on a line in the List Box. then clicking the command button. Are all numeric fields right justified? This is the default unless otherwise specified.e. All Rights Reserved C3: Protected . by clicking with the mouse. Assure that all windows have a consistent look and feel.Handout – Software Testing Combo Boxes Should allow text to be entered. should act in the same way as selecting and item in the list box. Validation Conditions: Does a failure of validation on every field cause a sensible user error message? Is the user required to fix entries.

Handout – Software Testing
Is validation consistently applied at screen level unless specifically required at field level? For all numeric fields check whether negative numbers can and should be able to be entered. For all numeric fields check the minimum and maximum values and also some midrange values allowable? For all character/alphanumeric fields check the field to ensure that there is a character limit specified and that this limit is exactly correct for the specified database size? Do all mandatory fields require user input? If any of the database columns don't allow null values then the corresponding screen fields must be mandatory. (If any field, which initially was mandatory, has become optional then check whether null values are allowed in this field.) Navigation Conditions: Can the screen be accessed correctly from the menu? Can the screen be accessed correctly from the toolbar? Can the screen be accessed correctly by double clicking on a list control on the previous creen? Can all screens accessible via buttons on this screen be accessed correctly? Can all screens accessible by double clicking on a list control be accessed correctly? Is the screen modal? (i.e.) Is the user prevented from accessing other functions when this screen is active and is this correct? Can a number of instances of this screen be opened at the same time and is this correct? Usability Conditions: Are all the dropdowns on this screen sorted correctly? Alphabetic sorting is the default unless otherwise specified. Is all date entry required in the correct format? Have all pushbuttons on the screen been given appropriate Shortcut keys? Do the Shortcut keys work correctly? Have the menu options that apply to your screen got fast keys associated and should they have? Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified. Are all read-only fields avoided in the TAB sequence? Are all disabled fields avoided in the TAB sequence? Can the cursor be placed in the microhelp text box by clicking on the text box with the mouse? Can the cursor be placed in read-only fields by clicking in the field with the mouse? Is the cursor positioned in the first input field or control when the screen is opened? Is there a default button specified on the screen? Does the default button work correctly? When an error message occurs does the focus return to the field in error when the user cancels it?
Page 24 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
When the user Alt+Tab's to another application does this have any impact on the screen upon return to the application? Do all the fields edit boxes indicate the number of characters they will hold by there length? e.g. a 30 character field should be a lot longer Data Integrity Conditions: Is the data saved when the window is closed by double clicking on the close box? Check the maximum field lengths to ensure that there are no truncated characters? Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact. Check maximum and minimum field values for numeric fields? If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers? If a set of radio buttons represents a fixed set of values such as A, B and C then what happens if a blank value is retrieved from the database? (In some situations rows can be created on the database by other functions, which are not screen based, and thus the required initial values can be incorrect.) If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values. Modes (Editable Read-only) Conditions: Are the screen and field colors adjusted correctly for read-only mode? Should a read-only mode be provided for this screen? Are all fields and controls disabled in read-only mode? Can the screen be accessed from the previous screen/menu/toolbar in read-only mode? Can all screens available from this screen be accessed in read-only mode? Check that no validation is performed in read-only mode. General Conditions: Assure the existence of the "Help" menu. Assure that the proper commands and options are in each menu. Assure that all buttons on all tool bars have a corresponding key commands. Assure that each menu command has an alternative (hot-key) key sequence, which will invoke it where appropriate. In drop down list boxes, ensure that the names are not abbreviations / cut short In drop down list boxes, assure that the list and each entry in the list can be accessed via appropriate key / hot key combinations. Ensure that duplicate hot keys do not exist on each screen Ensure the proper usage of the escape key (which is to undo any changes that have been made) and generates a caution message "Changes will be lost - Continue yes/no" Assure that the cancel button functions the same as the escape key.
Page 25 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
Assure that the Cancel button operates, as a Close button when changes have been made that cannot be undone. Assure that only command buttons, which are used by a particular window, or in a particular dialog box, are present. – (i.e) make sure they don't work on the screen behind the current screen. When a command button is used sometimes and not at other times, assures that it is grayed out when it should not be used. Assure that OK and Cancel buttons are grouped separately from other command buttons. Assure that command button names are not abbreviations. Assure that all field labels/names are not technical labels, but rather are names meaningful to system users. Assure that command buttons are all of similar size and shape, and same font & font size. Assure that each command button can be accessed via a hot key combination. Assure that command buttons in the same window/dialog box do not have duplicate hot keys. Assure that each window/dialog box has a clearly marked default value (command button, or other object) which is invoked when the Enter key is pressed - and NOT the Cancel or Close button Assure that focus is set to an object/button, which makes sense according to the function of the window/dialog box. Assure that all option buttons (and radio buttons) names are not abbreviations. Assure that option button names are not technical labels, but rather are names meaningful to system users. If hot keys are used to access option buttons, assure that duplicate hot keys do not exist in the same window/dialog box. Assure that option box names are not abbreviations. Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "Group Box" Assure that the Tab key sequence, which traverses the screens, does so in a logical way. Assure consistency of mouse actions across windows. Assure that the color red is not used to highlight active objects (many individuals are redgreen color blind). Assure that the user will have control of the desktop with respect to general color and highlighting (the application should not dictate the desktop background characteristics). Assure that the screen/window does not have a cluttered appearance Ctrl + F6 opens next tab within tabbed window Shift + Ctrl + F6 opens previous tab within tabbed window Tabbing will open next tab within tabbed window if on last field of current tab Tabbing will go onto the 'Continue' button if on last field of last tab within tabbed window Tabbing will go onto the next editable field in the window Banner style & size & display exact same as existing windows
Page 26 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Cognizant Technology Solutions. Assure that numeric fields with a blank in position 1 are processed or reported as an error. Assure that valid values are handles by the correct procedure. Assure that division by zero does not occur. highlighting the field with the error on it) Pressing continue while on the first tab of a tabbed window (assuming all fields filled correctly) will not open all the tabs. display all options on open of list box .should be no need to scroll Errors on continue will cause user to be returned to the tab and the focus should be on the field causing the error. Assure that out of cycle dates are validated correctly & do not cause errors/miscalculations.Handout – Software Testing If 8 or less options in a list box. All Rights Reserved C3: Protected .e the tab is opened. Page 27 ©Copyright 2007. Assure that invalid values are logged and reported. Assure that fields with a blank in the last position are processed or reported as an error an error. 29. generating "changes will be lost" message if necessary. Microhelp text for every enabled field & button Ensure all fields are disabled in read-only mode Progress messages on load of tabbed screens Return operates continue If retrieve on load of tabbed window fails window should not open Specific Field Tests Date Field Checks Assure that leap years are validated correctly & do not cause errors/miscalculations. Assure that both + and . Assure that 00 and 13 are reported as errors. 28.values are correctly processed. Assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations. Assure that Feb. (i. Numeric Fields Assure that lowest and highest values are handled correctly. Assure that Feb. 30 are validated correctly & do not cause errors/ miscalculations. Assure that month code 00 and 13 are validated correctly & do not cause errors/miscalculations. Assure that century change is validated correctly & does not cause errors/miscalculations. On open of tab focus will be on first editable field All fonts to be the same Alt+F4 will close the tabbed window and return you to main screen or previous screen (as appropriate). 30 is reported as an error.

Invalid data Different Check Box / Radio Box combinations Scroll Lists / Drop Down List Boxes Help Fill Lists and Scroll Tab Tab Sequence Shift Tab Page 28 ©Copyright 2007. continue saving changes or additions) Add View Change Delete Cancel .e.e.Standard Actions Examples of Standard Actions . Include at least one in-range value. Include valid characters. Include maximum and minimum range values. Include data items with first position blank. Include invalid characters & symbols. Validation Testing .(i.Handout – Software Testing Include value zero in all calculations. abandon changes or additions) Fill each field . Include lowest and highest values. All Rights Reserved C3: Protected . Include data items with last position blank. Assure that upper and lower values in ranges are handled correctly. Alpha Field Checks Use blank and non-blank data. Include out of range values above the maximum and below the minimum.(i. Cognizant Technology Solutions.Valid data Fill each field .Substitute your specific commands Add View Change Delete Continue .

Page 29 ©Copyright 2007. Cognizant Technology Solutions. All Rights Reserved C3: Protected .Handout – Software Testing Shortcut keys / Hot Keys Note: The following keys are used in some windows applications. and are included as a guide.

in the context for which they make sense. All Rights Reserved C3: Protected . Page 30 ©Copyright 2007. Cognizant Technology Solutions.Handout – Software Testing * These shortcuts are suggested for text formatting applications. Applications may use other modifiers for these operations.

To decide which test cycles to build. Each time your application changes. This test cycle includes tests that check that module in depth. Test Execution Test Execution is the heart of the testing process. You can run the cycle each time a new build is ready. Before a new version of a software product is released. and can include both manual and automated tests Example: You can create a cycle containing basic tests that run on each build of the application throughout development.Handout – Software Testing Regression Testing What is Regression Testing? Regression testing is the process of testing changes to computer programs to make sure that the older programming still works with the new changes. you will want to execute the relevant parts of your test plan in order to locate defects and assess quality. Cognizant Technology Solutions. you need to execute different tests in order to address specific goals. to determine the application's stability before beginning more rigorous testing. Example: You can create another set of tests for a particular module in your application. Create Test Cycles During this stage you decide the subset of tests from your test database you want to execute. A related group of tests is called a test cycle. refer to the testing goals you defined at the beginning of the process. The reason they might not work because changing or adding new code to a program can easily introduce errors into code that is not intended to be changed. At different stages of the quality assurance process. The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software. Usually you do not run all the tests at once. Also referred to as verification testing Regression testing is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors. It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity. Page 31 ©Copyright 2007. All Rights Reserved C3: Protected . the old test cases are run against the new version to make sure that all the old capabilities still work. Test department coders develop code test scenarios and exercises that will test new units of code after they have been written. Regression testing is a normal part of the program development process. Also consider issues such as the current state of the application and whether new functions have been added or modified.

During Automated Test Execution you create a batch of tests and launch the entire batch at once. A regression cycle includes sanity-level tests for testing the entire software. The tests in the cycle cover the entire application (breadth). Testing Tools runs the tests one at a time. Advanced cycle tests both breadth and depth. Change Request Initiating a Change Request A user or developer wants to suggest a modification that would improve an existing application. as well as in-depth tests for the specific area of the application that was modified. compare the application output with the expected output. and log the results. notices a problem with an application. Cognizant Technology Solutions. (for example. or if the expected result needs to be updated. or wants to recommend an enhancement. This cycle can be run when more time is available for testing. For each test step you assign either pass or fail status. containing both positive and negative checks. Regression cycle tests maintenance builds. It then imports results. All Rights Reserved C3: Protected . Normal cycle tests the system a little more in depth than the sanity cycle. enter input. You perform manual tests using the test steps. Testing Tools executes automated tests for you. and also test advanced options in the application (depth). Any major or minor request is considered a problem with an application and will be entered as a change request. Analyze Test Results After every test run one analyze and validate the test results. providing outcome summaries for each test. a letter is allowed to be entered in a number field) Change a modification of the existing application. you begin executing the tests in the cycle. This cycle can group medium-level tests. The goal of this type of cycle is to verify that a change to one part of the software did not break the rest of the application. Type of Change Request Bug the application works incorrectly or provides incorrect information. A test cycle is complete only when all tests-automatic and manual-have been run. (for example.Handout – Software Testing Following are examples of some general categories of test cycles to consider: Sanity cycle checks the entire system at a basic level (breadth. Run Test Cycles (Automated & Manual Tests) Once you have created cycles that cover your testing objectives. You use the application. This cycle should include basic-level tests containing mostly positive checks. And have to identify all the failed steps in the tests and to determine whether a bug has been detected. sorting the files alphabetically by the second field rather than numerically by the first field makes them easier to find) Enhancement Page 32 ©Copyright 2007. rather than depth) to see that it is functional and stable. With Manual Test Execution you follow the instructions in the test steps of each test.

First you report New bugs to the database. You can use data analysis tools such as re-ports and graphs in interpret bug data. You also make sure that the QA and development personnel involved in fixing the bug are notified. and closed. and provide all necessary information to reproduce. you report the bugs (or defects) that you detected. Below is a simple traceability matrix structure. fix. Bug Tracking involves two main stages: reporting and tracking. and end-users in all phases of the testing process. Software developers fix the Open bugs and assign them the status Fixed. Communication is an essential part of bug tracking. Information about bugs must be detailed and organized in order to schedule bug fixes and determine software release dates. High the application works. Bugs can be detected and reported by engineers. These bugs are given the status Open and are assigned to a member of the development team.Handout – Software Testing new functionality or item added to the application. Traceability Matrix A traceability matrix is created by associating requirements with the products that satisfy them. QA personnel test a new build of the application. Bug Tracking Locating and repairing software bugs is an essential part of software development. you record all the information necessary to reproduce and fix it. verified. The Quality Assurance manager or Project manager periodically reviews all New bugs and decides which should be fixed. Track and Analyze Bugs The lifecycle of a bug begins when it is reported and ends when it is fixed. The number of open or fixed bugs is a good indicator of the quality status of your application. All Rights Reserved C3: Protected . testers. If a bug is detected again. Report Bugs Once you execute the manual and automated tests in a cycle. a new report. The bugs are stored in a database so that you can manage them and analyze the status of your application. This also applies to any Section 508 infraction. it is Closed. job functions are impaired and there is no work around. If a bug does not reoccur. it is reopened. and follow up the bug. but this is necessary to perform a job. Critical the application does not work. Cognizant Technology Solutions. all members of the development and quality assurance team must be well informed in order to insure that bugs information is up to date and that the most important problems are addressed.Tests are associated with the requirements on which they are based and the product tested tomeet the requirement. (for example. When you report a bug. or a new button) Priority for the request Low the application works but this would make the function easier or more user friendly. a new field. There can be more things Page 33 ©Copyright 2007.

rewritten. Cognizant Technology Solutions. Traceability requires unique identifiers for each requirement and product. or the traceability corrected. Traceability ensures completeness.Handout – Software Testing included in a traceability matrix than shown below." Tracing S12 to its source makes it clear this requirement is erroneous: it must be eliminated. User requirement identifiers begin with "U" and system requirements with "S. Numbers for products are established in a configuration management (CM) plan. Traceability is also used in managing change and provides the basis for test planning. All Rights Reserved C3: Protected . that all lower level requirements derive from higher level requirements. The examples below show traceability between user and system requirements. Page 34 ©Copyright 2007. and that all higher level requirements are allocated to lower level requirements. SAMPLE TRACEABILITY MATRIX A traceability matrix is a report from the requirements database or repository.

Cognizant Technology Solutions. All Rights Reserved C3: Protected . not its parts Techniques can be structural or functional. Phases of Testing The primary objective of testing effort is to determine the conformance to requirements specified in the contracted documents.) Types and Phases of Testing Page 35 ©Copyright 2007. Determine their information needs and document the information that will be associated with the requirements when you set up your requirements database or repository. The integration of this code with the internal code is the important objective.Handout – Software Testing In addition to traceability matrices. Techniques can be used in any stage that tests the system as a whole (System testing. etc. Acceptance Testing. other reports are necessary to manage requirements. Unit testing. What goes into each report depends on the information needs of those receiving the report(s). Installation. Goal is to evaluate the system as a whole.

Cognizant Technology Solutions. All Rights Reserved C3: Protected .Handout – Software Testing Page 36 ©Copyright 2007.

All Rights Reserved C3: Protected . Cognizant Technology Solutions.Handout – Software Testing Page 37 ©Copyright 2007.

In fact. bottom-up. Second. The key is to Page 38 ©Copyright 2007. the larger the project. and finally assembling the highest level subsystems into the complete system. this is impractical for two major reasons. Integration may be performed all at once. the more important the integration strategy. To be most effective. However. Very small systems are often assembled and tested in one phase. satisfying any white box testing criterion would be very difficult. Performing only cursory testing at early integration phases and then applying a more rigorous criterion for the final stage is really just a variant of the high-risk "big bang" approach. critical piece first. All Rights Reserved C3: Protected . testing at each phase helps detect errors early and keep the system under control. top-down. performing rigorous testing of the entire software involved in each integration phase involves a lot of wasteful duplication of effort across phases. For most real systems. Cognizant Technology Solutions. because of the vast amount of detail separating the input data from the individual code modules. In a multi-phase integration. In general. then assembling subsystems into larger subsystems. beginning with assembling modules into lowlevel subsystems. the system would fail in so many places at once that the debugging and retesting effort would be impractical. an integration testing technique should fit well with the overall integration strategy.Handout – Software Testing Integration Testing One of the most significant aspects of a software development project is the integration strategy. most integration testing has been traditionally limited to ``black box'' techniques. or by first integrating functional subsystems and then integrating the subsystems in separate phases using any of the basic strategies. First. Large systems may require many integration phases.

Each of these views of integration testing may be appropriate for any given project. module and integration testing can be combined. verifying the details of each module's implementation in an integration context. so an integration testing method should be flexible enough to accommodate them all. for example. Cognizant Technology Solutions. assuming that the details within each module are accurate. Then. and then performing pure integration testing at higher levels. Many projects compromise. leads to an excessive amount of redundant testing. Page 39 ©Copyright 2007. As discussed in the previous subsection. Generalization of module testing criteria Module testing criteria can often be generalized in several possible ways to support integration testing. the most obvious generalization is to satisfy the module testing criterion in an integration context. integration testing concentrates entirely on module interactions. At the other extreme. It is important to understand the relationship between module testing and integration testing. combining module testing with the lowest level of subsystem integration testing. modules are rigorously tested in isolation using stubs and drivers before any integration is attempted. in effect using the entire program as a test driver environment for each module. However.Handout – Software Testing leverage the overall integration structure to allow rigorous testing at each phase while minimizing duplication of effort. this trivial kind of generalization does not take advantage of the differences between module and integration testing. All Rights Reserved C3: Protected . Applying it to each phase of a multiphase integration strategy. In one view.

and looping rules each remove one edge from the flow graph. since for poorlystructured code it may be hard to distinguish the ``top'' of the loop from the ``bottom. so that it is possible to exercise them independently during integration testing. The sequential rule eliminates sequences of non-call ("white dot") nodes. in which each statement is required to be exercised during module testing. the call rule states that function call ("black dot") nodes cannot be reduced. Since application of this rule removes one node and one edge from the flow graph. The idea behind design reduction is to start with a module control flow graph. Since the repetitive. Although not strictly a reduction rule. it leaves the cyclomatic complexity unchanged.'' For the rule to apply.Handout – Software Testing More useful generalizations adapt the module testing criterion to focus on interactions between modules rather than attempting to test all of the details of each module's implementation in an integration context. there must be a path from the module entry to the top of the loop and a path from the bottom of the loop to the module exit. Module design complexity Rather than testing all decision outcomes within a module independently. the approach is the same. The conditional rule eliminates conditional statements that do not contain calls in their bodies. All Rights Reserved C3: Protected . even very complex logic can be eliminated as long as it does not involve any module calls. and then use the resultant "reduced" flow graph to drive integration testing. they each reduce cyclomatic complexity by one. However. the appropriate generalization to the integration level requires that just the decision logic involved with calls to other modules be tested independently. structured testing at the integration level focuses on the decision outcomes that are involved with module calls. It is important to preserve the module's connectivity when using the looping rule. Cognizant Technology Solutions. The design reduction technique helps identify those decision outcomes. at which point the design reduction is complete. Figure below shows a systematic set of rules for performing design reduction. The remaining rules work together to eliminate the parts of the flow graph that are not involved with module calls. Page 40 ©Copyright 2007. it does simplify the graph so that the other rules can be applied. conditional. remove all control structures that are not involved with module calls. The statement coverage module testing criterion. By this process. Rules 1 through 4 are intended to be applied iteratively until none of them can be applied. The looping rule eliminates bottom-test loops that are not involved with module calls. Although the specifics of the generalization of structured testing are more detailed. Since structured testing at the module level requires that all the decision logic in a module's control flow graph be tested independently. The repetitive rule eliminates top-test loops that are not involved with module calls. can be generalized to require each module call statement to be exercised during integration testing.

Hierarchical design is most effective when the coupling among sibling components decreases as the component size increases. To form a completely flexible "statement testing" criterion. it is required that each statement be executed during the first phase (which may be anything from single modules to the entire Page 41 ©Copyright 2007.Handout – Software Testing Incremental integration Hierarchical system design limits each stage of development to a manageable effort. The remainder of this section extends the integration testing techniques of structured testing to handle the general case of incremental integration. including support for hierarchical design. To extend statement coverage to support incremental integration. All Rights Reserved C3: Protected . which simplifies the derivation of data sets that test interactions among components. avoiding redundant testing of previously integrated sub-components. The key principle is to test just the interaction among components at each integration stage. and it is important to limit the corresponding stages of testing as well. Cognizant Technology Solutions. it is required that all module call statements from one component into a different component be exercised at each integration stage.

All Rights Reserved C3: Protected . and that at each integration phase all call statements that cross the boundaries of previously integrated components are tested. Cognizant Technology Solutions. this limits the testing effort to a small fraction of the effort to cover each statement of the system at each integration phase. Given hierarchical integration stages with good cohesive partitioning properties.Handout – Software Testing program). Page 42 ©Copyright 2007.

Acceptance. but at all times they are informed by the business needs. since the design predicates decision to call module D from module B has been tested in a previous phase. System. It is similar to systems testing in that the whole system is checked but the important difference is the change in focus: Systems Testing checks that the system that was specified has been delivered. Acceptance Testing checks that the system delivers what was requested. To be of real use. Interface. It would take three tests to integrate this system in a single phase. The key is to perform design reduction at each integration phase using just the module call nodes that cross component boundaries. in general. and not the developer should always do acceptance testing. User Acceptance Testing is a critical phase of any 'systems' project and requires significant participation by the 'End Users'. The testing can be based upon the User Requirements Specification to which the system should conform. As in any system though. only two additional tests are required to complete the integration testing. Cognizant Technology Solutions. the testing should be planned in order to provide a realistic and adequate exposure of the system to all reasonably expected events. problems will arise and it is important to have determined what will be the expected and required responses from the various parties concerned. All Rights Reserved C3: Protected . The customer knows what is required from the system to achieve value in the business and is the only person qualified to make that judgment. The customer. an Acceptance Test Plan should be developed in order to plan precisely. The main types of software testing are: Component. the component module design complexity of module A is 1. Modules B and D are removed from consideration because they do not contain cross-component calls. Release. and the component module design complexity of module C is 2. Figure 7-7 illustrates the structured testing approach to incremental integration. acceptance testing is formal testing conducted to determine whether a system satisfies its acceptance criteria and thus whether the customer should accept the system. The test procedures that lead to formal 'acceptance' of new or changed systems. Acceptance Testing In software engineering. the means by which 'Acceptance' will be achieved. Page 43 ©Copyright 2007. including Users. and exclude from consideration all modules that do not contain any cross-component calls. However.Handout – Software Testing Structured testing can be extended to cover the fully general case of incremental integration in a similar manner. Modules A and C have been previously integrated. Factors influencing Acceptance Testing The User Acceptance Test Plan will vary from system to system but. The final part of the UAT can also include a parallel run to prove the system against the current system. yielding component-reduced graphs. Acceptance Testing checks the system against the "Requirements". and in detail. as have modules B and D. The forms of the tests may follow those in system testing.

or. we strongly advised that a range of examples are agreed in advance to ensure that there are no fundamental areas of disagreement. found during testing. In some cases. In any event. For example. in consultation with the executive sponsor of the project. Vendors and possibly Consultants / Contractors. Caution. Even where the severity levels and the responses to each have been agreed by all parties.g. colours. All Rights Reserved C3: Protected . N.B. These conditions need to be analyzed as they may. it must be agreed between End User and vendor. in terms of business / commercial impact. Because no system is entirely fault free. testing can continue and the system is likely to go live with only minimal departure from agreed business processes. you may demand that any problems in severity level 1. the maximum number of acceptable 'outstanding' in any particular category. Finally. In order to agree what such responses should be. both testing and live operations may progress. must be subjected to rigorous System Testing and. Again. the End Users and the Project Team need to develop and agree a range of 'Severity Levels'. these will be known in advance and your organization is forewarned. These levels will range from (say) 1 to 6 and will represent the relative severity. it is crucial to agree the Criteria for Acceptance. any and all fixes from the software developers. seek additional functionality which could be classified as scope creep. Page 44 ©Copyright 2007. Here is an example which has been used successfully. perhaps unintentionally. Medium Problem. Cognizant Technology Solutions. Minor Problem . '1' is the most severe. fonts. where appropriate Regression Testing. the allocation of a problem into its appropriate severity level can be subjective and open to question. of a problem with the system. receive priority response and that all testing will cease until such level 1 problems are resolved. 'Cosmetic' Problem e. Major Problem. and '6' has the least impact: 'Show Stopper' i. users may agree to accept ('sign off') the system subject to a range of conditions. but little or no changes to business processes are envisaged. if such features are key to the business requirements they will warrant a higher severity level. testing can continue but we cannot go into production (live) with this problem. or if there are. Critical Problem. To avoid the risk of lengthy and protracted exchanges over the categorization of problems.e. The users of the system. it is impossible to continue with the testing because of the severity of this error / bug. prior consideration of this is advisable. This problem should be corrected.Handout – Software Testing Project Team. testing can continue but live this feature will cause severe disruption to business processes in live operation. must then agree upon the responsibilities and required actions for each category of problem. pitch size However.

multiple languages. The independent test team is adequately staffed and trained in configuration testing. Preconditions Configuration testing can typically begin when the following preconditions hold: The configurability requirements to be tested have been specified. The relevant software components have passed unit testing.e.). etc. configuration testing can begin prior to the distribution of the software components onto the hardware components. fixed. Page 45 ©Copyright 2007. Multiple variants of the application exist. Support internationalization. Support personalization. The test environment is ready. Examples Typical examples include configuration testing of an application that must: Have multiple functional variants. currencies. The typical goals of configuration testing are to cause the application to fail to meet its configurability requirements so that the underlying defects can be identified. and prevented in the future.. Determine the effect of adding or modifying hardware resources such as: o o o o Memory Disk and tape resources Processors Load balancers Determine an optimal system configuration. Personalization Report these failures to the development teams so that the associated defects can be fixed. Cause failures concerning the configurability requirements that help identify defects that are not efficiently found during unit and integration testing: o o o Functional Variants. Internationalization (e.g. However. analyzed.Handout – Software Testing Configuration Testing & Installation Testing Configuration testing: Testing to determine whether the program operates properly when the software or hardware is configured in a required manner. to determine if it fulfills its configurability requirements). Objectives The typical objectives of configuration testing are to: Partially validate the application (i. All Rights Reserved C3: Protected . Cognizant Technology Solutions. taxes and tariffs. Software integration testing has started. time zones. The relevant system components have passed system integration testing..

Handout – Software Testing Completion Criteria Configuration testing is typically complete when the following postconditions hold: At least one configuration test suite exists for each configurability requirement. The test suites for every scheduled configurability requirement execute successfully on the appropriate configuration. Cognizant Technology Solutions. Tasks Configurability testing typically involves the independent test team performing the following testing tasks: Test Planning Test Reuse Test Design Test Implementation Test Execution Test Reporting Environments Configuration testing is performed on the following environments using the following techniques: Test Environment: Test Harness Work Products Configuration testing typically results in the production of all or part of the following work products from the test work product set: Documents: Project Test Plan Master Test List Test Procedures Test Report Test Summary Report Software and Data: Test Harness Test Scripts Test Suites Test Cases Test Data Phases Configuration testing typically consists of the following tasks being performed during the following phases: Page 46 ©Copyright 2007. All Rights Reserved C3: Protected .

Cognizant Technology Solutions. user acceptance test. and automated systems be validated for their intended use.Handout – Software Testing Guidelines The iterative and incremental development cycle implies that configuration testing is regularly performed in an iterative and incremental manner. installation testing is defined as any testing that takes place outside of the developer's controlled environment. reuse functional test cases as configuration test cases. Terms such as beta test. Configuration testing must be automated if adequate regression testing is to occur. Page 47 ©Copyright 2007. Installation testing is any testing that takes place at a user's site with the actual hardware and software that will be part of the installed system configuration. To avoid confusion. Quality System Regulations require installation and inspection procedures (including testing where appropriate) and documentation of inspection and testing to demonstrate proper installation. Guidance contained here is general in nature and is applicable to any installation testing. Installation testing: Testing to identify the ways in which the installation procedures lead to incorrect results. To the extent practical. All Rights Reserved C3: Protected . in some areas. The testing is accomplished through either actual or simulated use of the software being tested within the environment in which it is intended to function. However. and for the purposes of this document. manufacturing equipment must meet specified requirements. Likewise. Test planners should check with Soft Solutions International to determine whether there are any additional regulatory requirements for installation testing. and installation verification have all been used to describe installation testing. Terminology in this testing area can be confusing. site validation. there are specific site validation requirements that need to be considered in the planning of installation testing.

Handout – Software Testing Installation testing should follow a pre-defined plan with a formal summary of testing and a record of formal acceptance. If the developers are not involved. detection. fault testing (avoidance. if any. All Rights Reserved C3: Protected . These may include tests for a high volume of data. there should be an evaluation of the ability of the users of the system to understand and correctly interface with it. etc. Page 48 ©Copyright 2007. which are not apparent during more normal activities. Operators should be able to perform the intended operations and respond in an appropriate and timely manner to all alarms. and recovery). Records should be maintained during installation testing of both the system's capability to properly perform and the system's failures. implementation of safety requirements. Some of the evaluations that have been performed earlier by the software developer at the developer's site should be repeated at the site of actual use. tolerance. and the recording of all test outputs. There should be retention of documented evidence of all testing procedures. Launch. the definition of expected test results. Acceptance testing. If the developers are involved. and serviceability. Help determine the extent to which the application is ready for: o o o Beta testing. which are encountered. Report these failures to the development teams so that the associated defects can be fixed. Alpha testing and Beta testing Alpha testing is the launch testing consisting of the development organization’s initial internal dry runs of the application’s acceptance tests in the production environment. There should be evidence that hardware and software are installed and configured as specified. it is all the more important that the user have persons knowledgeable in software engineering who understand the importance of such matters as careful test planning. test input data and test results. errors. they may seamlessly carry over to the user's site the last portions of design-level systems testing. The developers of the software may or may not be involved in the installation testing. Objectives The typical objectives of alpha testing are to: Cause failures that only tend to occur in the production environment. The testing instructions should encourage use through the full range of operating conditions and should continue for a sufficient time to allow the system to encounter a wide spectrum of conditions and events in an effort to detect any latent faults. security. heavy loads or stresses. Cognizant Technology Solutions. error messages. The developer may be able to furnish the user with some of the test data sets to be used for this purpose. In addition to an evaluation of the system's ability to properly perform its intended functions. The revision of the system to compensate for faults detected during this installation testing should follow the same procedures and controls as any other software change. Measures should ensure that all system components are exercised during the testing and that the versions of these components are those specified. warnings.

Update the alpha testing subsection of Project Test Plan (PTP) Test Design: Select an adequate subset of the system test suites of test cases (both functional and quality) to be repeated on the production environment during alpha testing. Severity two defects that do not have adequate work arounds. The independent test team is adequately staffed. Completion Criteria Alpha testing is typically complete when the following post conditions hold: An initial version of the acceptance test suites exists. Environments Alpha testing is typically performed on the following environments with the following tools: o Production Environments None o o o o Page 49 ©Copyright 2007. The application has been ported to the production environment. Acceptance testing does not discover any: o o Severity one defects. Preconditions Execution of alpha tests can typically begin when the following preconditions hold: The application has passed all system tests. Tasks Typically involves the following teams performing the following testing tasks: Independent Test Team: o Test Planning: Determine alpha testing completion criteria. Cognizant Technology Solutions. The delivery phase has begun. All Rights Reserved C3: Protected . Test Reporting: Report failures that occurred during testing to the development teams so that the associated defects can be fixed. Test Execution: Execute the alpha test suites on the production environment. The production environment is ready. Test Implementation: Fix any defects in the test suites found during evaluation.Handout – Software Testing Provide input to the defect trend analysis effort. The acceptance tests execute on the production environment. The customer representative has approved these acceptance test suites.

Report these failures to the development teams so that the associated defects can be fixed. The delivery phase has begun. All Rights Reserved C3: Protected . Preconditions Beta test execution can typically begin when the following preconditions hold: The application has passed all system tests. Cognizant Technology Solutions. Definition Beta testing is the launch testing of the application in the production environment by a few select users prior to acceptance testing and the release of the application to its entire user community. Provide input to the defect trend analysis effort. Objectives The typical objectives of beta testing are to: Cause failures that only tend to occur during actual usage by the user community rather than during formal testing. Page 50 ©Copyright 2007. Launch. The production environment is ready. reuse the tests from system testing when performing alpha testing rather than producing new tests.Handout – Software Testing Phases Alpha testing typically involves the following tasks being performed during the following phases: Guidelines To the extent practical. The application has passed alpha testing. Help determine the extent to which the system is ready for: o o Acceptance testing. Obtain additional user community feedback beyond that received during usability testing.

All Rights Reserved C3: Protected . User Organizations: Page 51 ©Copyright 2007.Handout – Software Testing The application has been ported to the production environment. Completion Criteria Beta testing is typically complete when: The time period scheduled for beta testing ends.Pass on reported failures to developer organization. Tasks Beta testing typically involves the following producers performing the following testing tasks: Independent Test Team: o Test Planning . Cognizant Technology Solutions. Customer Organization: o o o o Environments Beta testing is typically performed on the following environments (limited to a select group of users) using the following tools: Production Environments: Client Environment Contact Center Environment Content Management Environment Data Center Environment Tools: Defect reporting tool. Test Reporting . The users have reported any failures observed to the development organization. Test Execution .Select beta test user group.Report failures to customer organization.Use application under normal conditions of operation. Test Implementation . Test Reporting . The selected group of users is ready.Update beta testing subsection of Project Test Plan (PTP). These failures have been passed on to the development teams.

Beta testing often uses actual live data rather than data created for testing purposes. Cognizant Technology Solutions. Test your Understanding 1. The testing that ensures that no unwanted changes were introduced is a) Unit Testing b) System Testing c) Acceptance Testing d) Regression Testing Answers: 1) a 2) d Page 52 ©Copyright 2007.Handout – Software Testing Phases Beta testing typically involves the following tasks being performed during the following phases: Guidelines Limit the user test group to users who are willing to use a lower quality version of the application in exchange for obtaining it early and having input into its iteration. Beta testing is critical if formal usability testing was not performed during system testing. Alpha testing is differentiated from beta testing by a) the location where the tests are conducted b) the types of tests conducted c) the people doing the testing d) the degree to which white-box techniques are used 2. All Rights Reserved C3: Protected .

then the tests will be trivial and the objects might pass the tests. any method that can break is a good candidate for having a unit test. "What will this bit of code do?" Or. In a sense. The danger of not implementing a unit test on every method is that the coverage may be incomplete. it is a little design document that says. Usually this is the case when the method involves a cluster of objects. if the scope is too broad. and they also identify those segments of code that are related. in the language of object oriented programming. People who revisit the code will use the unit tests to discover which objects are related. Unit tests will most likely be defined at the method level. but not relevant in most programming projects. but there will be no design of their interactions. or which objects form a cluster. If error handling is performed in a method. Unit tests that isolate clusters of objects for testing are doubly useful. "What will these clusters of objects do?" The crucial issue in constructing a unit test is scope. Likewise. Just because we don't test every method explicitly doesn't mean that methods can get away with not being tested. Need for Unit Test How do you know that a method doesn't need a unit test? First. because it may break at some time. The programmer is then reduced to testing-by-poking-around. so the art is to define the unit test on the methods that cannot be checked by inspection. Another good litmus test is to look at the code and see if it throws an error or catches an error. All Rights Reserved C3: Protected . Certainly. along with the expected results and pass/fail date. and then the unit test will be there to help you fix it. Usually this is a vision of a grand table with every single method listed. you will be able to: List different levels of testing Unit Testing Unit testing: Isn't that some annoying requirement that we're going to ignore? Many developers get very nervous when you mention unit tests. then there is a high chance that not every component of the new code will get tested. It's important. The programmer should know that their unit testing is complete when the unit tests cover at the very least the functional requirements of all the code. which is not an effective test strategy. The developer should know when this is the case. because they test for failures. Cognizant Technology Solutions. The unit test will motivate the code that you write. interactions of objects are the crux of any object oriented design. If the scope is too narrow. then that method can break.Handout – Software Testing Chapter 4: Levels of Testing Learning Objective After completing this chapter. can it be tested by inspection? If the code is simple enough that the developer can just look at it and verify its correctness then it is simple enough to not require a unit test. Page 53 ©Copyright 2007. Generally. The careful programmer will know that their unit testing is complete when they have verified that their unit tests cover every cluster of objects that form their application. Hence: Unit tests isolate clusters of objects for future developers.

To test particular functions or code modules. Cognizant Technology Solutions. Not always easily done unless the application has a well-designed architecture with tight code.Handout – Software Testing Life Cycle Approach to Testing Testing will occur throughout the project lifecycle i.. Typically done by the programmer and not by testers. Levels of Unit Testing UNIT 100% code coverage INTEGRATION SYSTEM ACCEPTANCE MAINTENANCE AND REGRESSION Concepts in Unit Testing: The most 'micro' scale of testing.e. The main Objective to Unit Testing are as follows : To execute a program with the intent of finding an error.. from Requirements till User Acceptance Testing. All Rights Reserved C3: Protected . As it requires detailed knowledge of the internal program design and code. To uncover an as-yet undiscovered error . and Prepare a test case with a high probability of finding an as-yet undiscovered error. Types of Errors detected The following are the Types of errors that may be caught Error in Data Structures Performance Errors Logic Errors Validity of alternate and exception flows Identified at analysis/design stages Page 54 ©Copyright 2007.

. Page 55 ©Copyright 2007.Handout – Software Testing Unit Testing – Black Box Approach Field Level Check Field Level Validation User Interface Check Functional Level Check Unit Testing – White Box Approach STATEMENT COVERAGE DECISION COVERAGE CONDITION COVERAGE MULTIPLE CONDITION COVERAGE (nested conditions) CONDITION/DECISION COVERAGE PATH COVERAGE Unit Testing – Field Level Checks Null / Not Null Checks Uniqueness Checks Length Checks Date Field Checks Numeric Checks Negative Checks Unit Testing – Field Level Validations Test all Validations for an Input field Date Range Checks (From Date/To Date’s) Date Check Validation with System date Unit Testing – User Interface Checks Readability of the Controls Tool Tips Validation Ease of Use of Interface Across Tab related Checks User Interface Dialog GUI compliance checks Unit Testing . All Rights Reserved C3: Protected .Functionality Checks Screen Functionalities Field Dependencies Auto Generation Algorithms and Computations Normal and Abnormal terminations Specific Business Rules if any. Cognizant Technology Solutions.

Basic block coverage is the same as statement coverage except the unit of code measured is each sequence of non-branching statements. segment coverage and basic block coverage. Also known as: line coverage.Other Measures Function coverage Loop coverage Race coverage Execution of Unit Tests Design a test case for every statement to be executed. This measure reports whether each executable statement is encountered.Handout – Software Testing Unit Testing . Page 56 ©Copyright 2007. Cognizant Technology Solutions. All Rights Reserved C3: Protected . Select the unique set of test cases.

Cognizant Technology Solutions.Handout – Software Testing Page 57 ©Copyright 2007. All Rights Reserved C3: Protected .

Performance profilers commonly implement this measure. All Rights Reserved C3: Protected . Method for Statement Coverage Design a test-case for the pass/failure of every decision point Select unique set of test cases Page 58 ©Copyright 2007.Handout – Software Testing Unit Testing Flow : Advantage of Unit Testing Can be applied directly to object code and does not require processing source code. Cognizant Technology Solutions. Disadvantage of Unit Testing Insensitive to some control structures (number of iterations) Does not report whether loops reach their termination condition Statement coverage is completely insensitive to the logical operators (|| and &&).

Reports whether every possible combination of boolean sub-expressions occurs. basis path coverage. especially for very complex Boolean expressions Number of test cases required could vary substantially among conditions that have similar complexity Condition/Decision Coverage is a hybrid measure composed by the union of condition coverage and decision coverage. when present. Additionally. this measure includes coverage of switch-statement cases. exception handlers. all-edges coverage. the sub-expressions are separated by logical-and and logical-or. It has the advantage of simplicity but without the shortcomings of its component measures This measure reports whether each of the possible paths in each function have been followed.Handout – Software Testing This measure reports whether Boolean expressions tested in control structures (such as the if-statement and while-statement) evaluated to both true and false. and interrupt handlers. Method for Condition Coverage: Test if every condition (sub-expression) in decision for true/false Select unique set of test cases. Cognizant Technology Solutions. "Basis path" testing selects paths that achieve decision coverage. Disadvantage: Tedious to determine the minimum set of test cases required. The test cases required for full multiple condition coverage of a condition are given by the logical operator truth table for the condition. All Rights Reserved C3: Protected . Also known as predicate coverage. Predicate coverage views paths as possible combinations of logical conditions Path coverage has the advantage of requiring very thorough testing Page 59 ©Copyright 2007. Reports the true or false outcome of each Boolean sub-expression. A path is a unique sequence of branches from the function entry to the exit. As with condition coverage. Advantage: Simplicity without the problems of statement coverage Disadvantage This measure ignores branches within boolean expressions which occur due to shortcircuit operators. decisionpath testing. The entire Boolean expression is considered one true-or-false predicate regardless of whether it contains logical-and or logical-or operators. separated by logical-and and logical-or if they occur. Condition coverage measures the sub-expressions independently of each other. Also known as: branch coverage.

client. shallow testing finds gross deficiencies in a test suite quickly. twice and more than twice (consecutively). Loop Coverage This measure reports whether you executed each loop body zero times. and more than once. Specifically. Broad. All Rights Reserved C3: Protected . loop coverage reports whether you executed the body exactly once. Useful for testing multi-threaded programs such as in an operating system.e. Helps detect failure to synchronize access to resources. System Integration System integration testing is the integration testing of two or more system components.Handout – Software Testing Function Coverage: This measure reports whether you invoked each function or procedure. Kinds of Integration Testing Integration testing includes the following kinds of testing: Commercial Component Integration Commercial component integration testing is the integration testing of multiple commercialoff.theshelf (COTS) software components to determine if they are not interoperable (i. and database Page 60 ©Copyright 2007. if they contain any interface defects).g. The valuable aspect of this measure is determining whether while-loops and for-loops execute more than once. exactly once. Objectives The typical objectives of integration testing are to: Determine if components will work properly together.. system integration testing is the testing of software components that have been distributed across multiple platforms (e. For do-while loops. Software Integration Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects.. Integration Testing Integration testing is the testing of a partially integrated application to identify defects involving the interaction of collaborating components. Race Coverage This measure reports whether multiple threads execute the same code at the same time. Cognizant Technology Solutions. application server. web server. Identify defects that are not easily identified during unit testing. It is useful during preliminary testing to assure at least some coverage in all areas of the software. information not reported by others measure.

an online casino or games testing. In other words. In this paper we examine the results of applying several types of Poisson-process models to the development of a large system for which system test was performed in two parallel tracks. We test for errors that users are likely to make as they interact with the application as well as your application’s ability to trap errors gracefully. railway. whether testing a financial system. The main goal is rather to demonstrate the discrepancies of the product from its requirements and its documentation. defects involving distribution and back-office integration). using different strategies for test data selection. development costs and improved 'time to market' for new systems. and nevertheless. Making this function more effective can deliver a range of benefits including reductions in risk. ``Did we build the product right?'' However. like a mulituser network or whetever. system testing does not only deal with this more economical problem. Therefore the program has to be given completely. It is often agreed that testing is essential to manufacture reliable products. ``Did we build the right product?'' and not just. The difference between function testing and system testing is that now the focus is on the whole application and its environment . while this is one of the most incomplete test methods. ecommerce. All Rights Reserved C3: Protected . it is beyond doubt that this test cannot be done completely. Moreover. the validation process is close to other activities such as conformance. automotive. System Testing For most organizations.e. Systems with software components and software-intensive systems are more and more complex everyday. it also contains some aspects that are orientated on the word ``system'' . and aeronautical and space. A number of time-domain software reliability models attempt to predict the growth of a system's reliability during the system test phase of the development life cycle. These techniques can be applied flexibly. the validation process does not often receive the required attention. software and system testing represents a significant element of a project's cost in terms of money and management time. We will test that the functionality of your systems meets with your specifications.. Guidelines The iterative and incremental development cycle implies that integration testing is regularly performed in an iterative and incremental manner. However. integrating with which-ever type of development methodology you are applying. This does not mean that now single functions of the whole program are tested. acceptance and qualification testing. it is one of the most important. Once again.Handout – Software Testing server) to produce failures caused by system integration defects (i. Industry sectors such as telecom. Cognizant Technology Solutions. this again includes the question. are good examples. Integration testing must be automated if adequate regression testing is to occur. Even security guide lines have to be included. because this would be too redundant. Page 61 ©Copyright 2007. This means that those tests should be done in the environment for which the program was designed.

however. when appropriate. All Rights Reserved C3: Protected . also encompass many other types of testing. speed.test adherence to standards Page 62 ©Copyright 2007. data. Recovery testing . users. installation. etc. not its parts Techniques can be structural or functional Techniques can be used in any stage that tests the system as a whole (acceptance. Your test strategy must take into consideration the risks to your organisation. etc.test how the system fits in with existing operations and procedures in the user organization Compliance testing . has been proven over the last 3decades to deliver real business benefits including: These benefits are achieved as a result of some fundamental principles of testing. precision. and can. commercial and technical. etc. System Testing Techniques Goal is to evaluate the system as a whole. increased independence naturally increases objectivity.Handout – Software Testing System Testing is more than just functional testing. etc. for example.test performance in terms of speed. Cognizant Technology Solutions. You will have a personal interest in its success in which case it is only human for your objectivity to be compromised. Execution testing.test larger-than-normal capacity in terms of transactions. as a part of software engineering. Operations testing .test how the system recovers from a disaster. such as: Security Load/stress Performance Browser compatibility Localisation Need for System Testing Effective software testing.) Techniques not mutually exclusive Structural techniques Stress testing . how it handles corrupted data.

test required error-handling functions (usually user error) Manual-support testing . including high. component.includes user documentation Intersystem handling testing .each truth statement is exercised both true and false Expression testing .feed same input into two versions of the system to make sure they Produce the same output Unit Testing Goal is to evaluate some piece (file.) in isolation Techniques can be structural or functional In practice.test required control mechanisms Parallel testing . low.design test cases that use input values that represent special situations Output domain testing .ensure the set of test cases exercises every statement at least once Branch testing . Cognizant Technology Solutions.test that the system can be used properly .partition the range of allowable input so that the program is expected to behave similarly for all inputs in a given partition.each branch of an if/then statement is exercised Conditional testing .choose test cases with input values at the boundary (both inside and outside) of the allowable range Syntax checking .pick test cases that will produce output at the extremes of the output domain Structural techniques Statement testing . etc.test security requirements Functional techniques Requirements testing .pick test cases representative of the range of allowable input.test that the system is compatible with other systems in the environment Control testing . module.choose test cases that violate the format rules for input Special values .fundamental form of testing . it’s usually ad-hoc and looks a lot like debugging More structured approaches exist Functional techniques Input domain testing . and average values Equivalence partitioning .makes sure the system does what it’s required to do Regression testing .every part of every expression is exercised Path testing . program. All Rights Reserved C3: Protected .every path is exercised (impossible in practice) Error-based techniques Page 63 ©Copyright 2007.make sure unchanged functionality remains unchanged errorhandling testing .Handout – Software Testing Security testing . then pick a test case from each partition Boundary value .

System testing can occur in parallel with integration test. then test until they are all found Mutation testing . In general. an independent test group b. The customer Answers: 1) a 2) b Page 64 ©Copyright 2007.create mutants of the program by making single changes.put a certain number of known faults into the code. none of the above 2). All Rights Reserved C3: Protected . then tests a new product until the number of defects found approaches the expected number SUMMARY Testing irrespective of the phases of testing should encompass the following: Cost of Failure associated with defective products getting shipped and used by customer is enormous To find out whether the integrated product work as per the customer requirements To evaluate the product with an independent perspective To identify as many defects as possible before the customer finds To reduce the risk of releasing the product Hence the system Test phase should begin once modules are integrated enough to perform tests in a whole system environment.an organization keeps records of the average numbers of defects in the products it produces. especially with the top-down method. unit testing is performed by: a. the software engineer c. both black-and-white-box oriented d. SQA d. Test your Understanding 1). then run test cases until all mutants have been killed Historical test data . you can estimate whether or not you’ve found all of them or not Fault seeding . white-box oriented b. Unit testing is predominantly a. black-box oriented c. Cognizant Technology Solutions.Handout – Software Testing Basic idea is that if you know something about the nature of the defects in the code.

It is an instance of the xUnit architecture for unit testing frameworks. Also. JUnit tests do not require human judgment to interpret. and it is easy to run many of them at the same time. Money m14CHF= new Money(14. JUNIT Testing .Handout – Software Testing Chapter 5: JUnit Testing Learning Objective After completing this chapter. When you need to test something. Override the method runTest() When you want to check a value. they don't compose nicely. you will be able to: Write a Junit Testing. here is what you do: Create an instance of Test Case: Create a constructor which accepts a String as a parameter and passes it to the superclass. call assertTrue() and pass a boolean that is true if the test succeeds For example. "CHF"). You can change debug expressions without recompiling. write: public void testSimpleAdd() { Money m12CHF= new Money(12. to test that the sum of two Moneys with the same currency contains a value which is the sum of the values of the two Moneys. JUnit features include: Assertions for testing expected results Test fixtures for sharing common test data Test suites for easily organizing and running tests Graphical and textual test runners JUnit was originally written by Erich Gamma and Kent Beck Simple Test Case How do you write testing code? The simplest way is as an expression in a debugger. and you can wait to decide what to write until you have seen the running objects. Cognizant Technology Solutions. You can also write test expressions as statements which print to the standard output stream.you can only execute one debug expression at a time and a program with too many print statements causes the dreaded "Scroll Blindness". Both styles of tests are limited because they require human judgment to analyze their results. All Rights Reserved C3: Protected .Introduction JUnit is a simple framework to write repeatable tests. Page 65 ©Copyright 2007. "CHF").

add(m14CHF). When you are writing tests you will often find that you spend more time writing the code to set up the fixture than you do in actually testing values. Each case will send slightly different messages or parameters to the fixture and will check for different results. This set of objects is called a test fixture. "CHF"). When you have a common fixture. to write several test cases that want to work with different combinations of 12 Swiss Francs. All Rights Reserved C3: Protected . Money result= m12CHF. } If you want to write a test similar to one you have already written. Often. you can make writing the fixture code easier by paying careful attention to the constructors you write.Handout – Software Testing Money expected= new Money(26. write a Fixture instead. a much bigger savings comes from sharing fixture code. f14CHF= new Money(14. protected void setUp() { f12CHF= new Money(12.equals(result)). private Money f28USD. here is what you do: Create a subclass of TestCase Create a constructor which accepts a String as a parameter and passes it to the superclass. 14 Swiss Francs. To some extent. Page 66 ©Copyright 2007. Add an instance variable for each part of the fixture Override setUp() to initialize the variables Override tearDown() to release any permanent resources you allocated in setUp For example. create a Suite. "CHF"). "CHF"). and 28 US Dollars. you can write as many Test Cases as you'd like. first create a fixture: public class MoneyTest extends TestCase { private Money f12CHF. private Money f14CHF. f28USD= new Money(28. Fixture What if you have two or more tests that operate on the same or similar sets of objects? Tests need to run against the background of a known set of objects. However. assertTrue(expected. Cognizant Technology Solutions. When you want to run more than one test. "USD"). } } Once you have the Fixture in place. you will be able to use the same fixture for several different tests.

write: public void testMoneyMoneyBag() { // [12 CHF] + [14 CHF] + [28 USD] == {[26 CHF][28 USD]} Money bag[]= { f26CHF. assertEquals(expected. All Rights Reserved C3: Protected . TestResult result= suite. For example. suite. or it can't be invoked through reflection.Create an instance of the TestCase class and pass the name of the test case method to the constructor. Cognizant Technology Solutions. Suite How do you run several tests at once? As soon as you have two tests. suite. you execute: TestResult result= (new MoneyTest("testMoneyMoneyBag")). to run a single test case. However. you'll want to run them together.add(f28USD. f28USD }. Page 67 ©Copyright 2007. } Create an instance of of MoneyTest that will run this test case like this: new MoneyTest("testMoneyMoneyBag") When the test is run.run(). Once you have several tests. You write test cases for a Fixture the same way.addTest(new MoneyTest("testMoneyEquals")).run(). but you would quickly grow tired of that.addTest(new MoneyTest("testSimpleAdd")). To create a suite of two test cases and run them together. MoneyBag expected= new MoneyBag(bag). the name of the test is used to look up the method to run.add(f14CHF))). JUnit provides an object. Be sure to make it public. For example. To do so you pass the class of your Test Case to the TestSuite constructor. TestSuite which runs any number of test cases together. execute: TestSuite suite= new TestSuite(). Another way is to let JUnit extract a suite from a TestCase. to test the addition of a Money and a MoneyBag. f12CHF.override runTest in an anonymous subclass of TestCase. after a few such tests you would notice that a large percentage of your lines of code are sacrificed to syntax. JUnit provides a more concise way to write a test against a Fixture. Instead.Handout – Software Testing Test Case How do you write and invoke an individual test case when you have a Fixture? Writing a test case without a fixture is simple. Here is what you do: Write the test case method in the fixture class. You could run the tests one at a time yourself. organize them into a Suite. by making a subclass of TestCase for your set up code and then making anonymous subclasses for the individual test cases.

suite()).addTest(new MoneyTest("testSimpleAdd")). JUnit provides tools to define the suite to be run and to display its results. TestRunner How do you run your tests and collect their results? Once you have a test suite.TestRunner or junit. TestResult result= suite.addTest(new MoneyTest("testMoneyEquals")). All Rights Reserved C3: Protected . A list of failed tests. A run button to start the test.run(). JUnit provides both a graphical and a textual version of a TestRunner tool. TestResult result= suite. Cognizant Technology Solutions.class). } If a TestCase class doesn't define a suite method a TestRunner will extract a suite and fill it with all the methods starting with "test". A failure is anticipated and checked for with assertions. suite. For example.addTest(Kent. return suite. JUnit distinguishes between failures and errors. to make a MoneyTest suite available to a TestRunner. Otherwise the automatic suite extraction is the preferred way. A progress indicator that turns from red to green in the case of a failed test.run(). suite.suite()). The graphical user interface presents a window with: A field to type in the name of a class with a suite method. In the case of an unsuccessful test JUnit reports the failed tests in a list at the bottom. TestSuites don't only have to contain TestCases.Start it by typing java junit. They contain any object that implements the Test interface. you can create a TestSuite in your code and I can create one in mine. You make your suite accessible to a TestRunner tool with a static method suite that returns a test suite For example. and we can run them together by creating a TestSuite that contains both: TestSuite suite= new TestSuite(). suite.Handout – Software Testing TestSuite suite= new TestSuite(MoneyTest. Errors are unanticipated problems like an Page 68 ©Copyright 2007. Use the manual way when you want a suite to only contain a subset of the test cases. It avoids you having to update the suite creation code when you add a new test case.awtui. you'll want to run it.TestRunner. suite. add the following code to MoneyTest: public static Test suite() { TestSuite suite= new TestSuite().swingui.addTest(Erich.

There is a batch interface to JUnit. Page 69 ©Copyright 2007. This is tedious and time consuming. This LoadingTestCollector reloads all your classes for each test run. To use it typejava junit.TestRunner. As an alternative JUnit's AWT and Swing UIs use junit.TestRunner followed by the name of the class with a suite method at an operating system prompt.runner. Cognizant Technology Solutions.textui. The following figure shows an example of a failed test. to start the batch TestRunner for MoneyTest. write: public static void main(String args[]) { junit.jar file is on your CLASSPATH. For using either the graphical or the textual version make sure that the junit. All Rights Reserved C3: Protected . } With this definition of main you can run your tests by simply typing java MoneyTest at an operating system prompt.This feature can be disabled by unchecking the 'Reload classes every run' checkbox. In other environments you have to restart the graphical version for each run. For example.textui.run(suite()).LoadingTestCollector . In a dynamic programming environment like VisualAge for Java which supports hot code update you can leave the JUnit window up all the time. An alternative way to invoke the batch interface is to define a main method in your TestCase class. also.Handout – Software Testing ArrayIndexOutOfBoundsException. The batch interface shows the result as text output.

A detailed test plan and schedule is prepared with key test responsibilities being indicated. The Testing strategy should define the objectives of all test stages and the techniques that apply. Test specifications – required for all levels of testing and covering all categories of test. Cognizant Technology Solutions. The status of the configuration items should be reviewed against the phase plans and test progress reports prepared providing some assurance of the verification and validation activities. Unit. All Rights Reserved C3: Protected . Test planning – the requirements definition and design specifications facilitate in the identification of major test items and these may necessitate the test strategy to be updated. The test environment should also be under configuration control and test data and results stored for future evaluation. The testing strategy also forms the basis for the creation of a standardized documentation set. integration and system testing – configuration items are verified against the appropriate specifications and in accordance with the test plan. Test monitoring and assessment – ongoing monitoring and assessment of the integrity of the development and construction. Test management is also concerned with both test resource and test environment management. It is the role of test management to ensure that new or modified service products meet the business requirements for which they have been developed or enhanced. Test Approach/Test Architecture are the acronyms for Test Strategy. Test organization also involves the determination of configuration standards and the definition of the test environment. The required outcome of each test must be known before the test is attempted. you will be able to: Create a test plans and test cases Test Strategy and Test Plan Introduction This Document entails you towards the better insight of the Test Strategy and its methodology. Page 70 ©Copyright 2007. the test strategy.Handout – Software Testing Chapter 6: Testing Artifacts Learning Objective After completing this chapter. Any test support tools introduced should be aligned with. and facilitates communication of the test process and its implications outside of the test discipline. Key elements of Test Management: Test organization –the set-up and management of a suitable test organizational structure and explicit role definition. and in support of. high level test phase plans prepared and resource schedules considered. The project framework under which the testing activities will be carried out is reviewed.

e-commerce testing may involve new user interfaces and a business focus on usability may mean that the organization must review its testing strategies. The testing to be performed. A common criticism of construction programmers is that insufficient time is frequently allocated to the testing and commissioning of the building systems together with the involvement and subsequent training of the Facilities Management team. Cognizant Technology Solutions. stress and security etc? Does the test plan prescribe the approach to be taken for intended test activities. The Project Sponsor should ensure that the professional team and the contractor consider realistically how much time is needed. Resource and facility requirements. Fitness for purpose checklist: Is there a documented testing strategy that defines the objectives of all test stages and the techniques that may apply. Page 71 ©Copyright 2007. Product assurance may oversee some of the test activity and may participate in process reviews. Testing and commissioning is often considered by teams as a secondary activity and given a lower priority particularly as pressure builds on the program towards completion.g. identifying: The items to be tested. Risks requiring contingency measures? Are test processes and practices reviewed regularly to assure that the testing processes continue to meet specific business needs? For example. Sufficient time must be dedicated to testing and commissioning as ensuring the systems function correctly is fairly fundamental to the project’s success or failure. It is possible to gain greater control of this process and the associated risk through the use of specialists such as Systems Integration who can be appointed as part of the professional team.Handout – Software Testing Product assurance – the decision to negotiate the acceptance testing program and the release and commissioning of the service product is subject to the ‘product assurance’ role being satisfied with the outcome of the verification activities. All Rights Reserved C3: Protected . Reporting requirements. non-functional testing and the associated techniques such as performance. Evaluation criteria. Test schedules. The time necessary for testing and commissioning will vary from project to project depending upon the complexity of the systems and services that have been installed. Traditionally the responsibility for testing and commissioning is buried deep within the supply chain as a sub-contract of a subcontract. e.

Unable to handle Complex Decisions. Understand the underlying Algorithm. Scenarios may be corrupted. Create complex scenarios and compare them. Review Documentation and Help. . Test for sensitivity to user Error. Capability test each major function. Page 72 ©Copyright 2007. Generate large number of decision scenarios. Simulate the Algorithm in parallel. People will use the Product Incorrectly Incorrect comparison of scenarios. All Rights Reserved C3: Protected Based on the Key Potential Risks o o o o o o o o o o o o Determination of Actual Risk. Suggestion of Wrong Ideas. Test Strategy – Selection Selection of the Test Strategy is based on the following factors Product o Test Strategy based on the Application to help people and teams of people in making decisions.Handout – Software Testing Test Strategy Flow: Test Cases and Test Procedures should manifest Test Strategy. Cognizant Technology Solutions.

Test the product for the risk of silent failures or corruptions in decision analysis. Test with decision scenarios that are near the limit of complexity allowed by the product Compare complex scenarios. All Rights Reserved C3: Protected . Page 73 ©Copyright 2007. Create a means to generate and apply large numbers of decision scenarios to the product. General Testing Strategies Top-down Bottom-up Thread testing Stress testing Back-to-back testing Need for Test Strategy The objective of testing is to reduce the risks inherent in computer systems. The system concerns on risks then establish the objectives for the test process. Issues in Execution of the Test Strategy The difficulty of understanding and simulating the decision algorithm The risk of coincidal failure of both the simulation and the product.Handout – Software Testing Test Strategy Execution: Understand the decision Algorithm and generate the parallel decision analyzer using the Perl or Excel that will function as a reference for high volume testing of the app. Cognizant Technology Solutions. This will be done using the GUI test Automation system or through the direct generation of Decide Right scenario files that would be loaded into the product during test. and the design of the user interface and functionality for its sensitivity to user error. The strategy must address the risks and present a process that can reduce those risks. The two components of the testing strategy are the Test Factors and the Test Phase. The difficulty of automating decision tests. Review the Documentation.

Developing a Test Strategy The test Strategy will need to be customized for any specific software system. The applicable test factors would be listed as the phases in which the testing must occur. All Rights Reserved C3: Protected . Select and rank Test Factors Identify the System Developmental Phases Identify the Business risks associated with the System under Development. The test phase will vary based on the testing methodology used. Four test steps must be followed to develop a customized test strategy. For example the test phases in as traditional waterfall life cycle methodology will be much different from the phases in a Rapid Application Development methodology. Not all the test factors will be applicable to all software systems. The development team will need to select and rank the test factors for the specific software systems being developed.Handout – Software Testing Test Factor – The risk or issue that needs to be addressed as part of the test strategy. Cognizant Technology Solutions. Test Phase – The Phase of the systems development life cycle in which testing will occur. The strategy will select those factors that need to be addressed in the testing of a specific application system. Place risks in the Matrix Page 74 ©Copyright 2007.

The completed document will help people outside the test group understand the 'why' and 'how' of product validation. the testing tasks. Test Plan A Test Plan can be defined as a document that describes the scope. Cognizant Technology Solutions. deadlines and deliverables for the project. and any risks requiring contingency planning.Handout – Software Testing Conclusion: Test Strategy should be developed in accordance with the business risks associated with the software when the test team develop the test tactics. It is in this respect that reviews and a sign-off are very important since it means that everyone is in agreement of the contents of the test plan and this also helps in case of any dispute during the course of the project (especially between the developers and the testers). The system accordingly focuses on risks thereby establishes the objectives for the test process. It identifies test items. responsibilities. who will do each task. the features to be tested. resources and schedule of intended test activities. The main purpose of preparing a Test Plan is that everyone concerned with the project are in sync with regards to the scope. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. All Rights Reserved C3: Protected . Purpose of preparing a Test Plan A Test Plan is a useful way to think through the efforts needed to validate the acceptability of a software product. Thus the Test team needs to acquire and study the test strategy that should question the following: What is the relationship of importance among the test factors? Which of the high level risks are the most significant? What damage can be done to the business if the software fails to perform correctly? What damage can be done to the business if the business if the software is not completed on time? Who are the individuals most knowledgeable in understanding the impact of the identified business risks? Hence the Test Strategy must address the risks and present a process that can reduce those risks. approach. Contents of a Test Plan Purpose Scope Test Approach Entry Criteria Resources Tasks / Responsibilities Exit Criteria Schedules / Milestones Page 75 ©Copyright 2007.

starting the web server / app server. Cognizant Technology Solutions. Entry Criteria This section explains the various steps to be performed before the start of a test (i. For example: Timely environment set up. Page 76 ©Copyright 2007.) prerequisites. database. All Rights Reserved C3: Protected . Schedules / Milestones This sections deals with the final delivery date and the various milestone dates to be met in the course of the project.Handout – Software Testing Hardware / Software Requirements Risks & Mitigation Plans Tools to be used Deliverables References Procedures Templates Standards/Guidelines Annexure Sign-Off Contents (in detail) Purpose This section should contain the purpose of preparing the test plan Scope This section should talk about the areas of the application which are to be tested by the QA team and specify those areas which are definitely out of scope (screens. mainframe processes etc). Resources This section should list out the people who would be involved in the project and their designation etc. successful implementation of the latest build etc. restoring system to pre-test environment.e. database refresh etc. Test Approach This would contain details on how the testing is to be performed and whether any specific strategy is to be followed (including configuration management). Tasks / Responsibilities This section talks about the tasks to be performed and the responsibilities assigned to the various members in the project. Exit criteria Contains tasks like bringing down the system / server.

Each separate test should be given a unique reference number which will identify the Business Process being recorded. Status Reports.) templates used for reports. Test Director. Test Scripts etc.Introduction A System is programmed by its data. These could include Test Plans. Templates for all these could also be attached.e.g. Preparation of the data can help to focus the business where requirements are vague. Test Matrices.g. Sign-Off This should contain the mutual agreement between the client and the QA team with both leads / managers signing off their agreement on the Test Plan. end of the project etc. correctly chosen. connectivity related issues etc. Its contents.) QView Project related documents (RSD. References Procedures Templates (Client Specific or otherwise) Standards / Guidelines (e. Test Data Preparation . It is recommended that a full test environment be set up for use in the applicable circumstances. Test data should however. and good data can help improve functional testing. FSD etc) Annexure This could contain embedded documents or links to documents which have been / will be used in the course of testing (e.) daily. Actual customer names or contact details should also not be used for such tests. Test Procedure.Handout – Software Testing Hardware / Software Requirements This section would contain the details of PC’s / servers required (with the configuration) to install the application or perform the testing. weekly. All Rights Reserved C3: Protected .g. test cases etc. The first stage of any recogniser development project is data preparation. PCOM. ADD.) WinRunner. the persons involved in the testing Page 77 ©Copyright 2007. specific software that needs to be installed on the systems to get the application running or to connect to the database. Good test data can be structured to improve understanding and testability. WinSQL. be prepared which is representative of normal business transactions. start of the project. Risks & Mitigation Plans This section should list out all the possible risks that can arise during the testing and the mitigation plans that the QA team plans to implement incase the risk actually turns into a reality. can reduce maintenance effort and allow flexibility. Functional testing can suffer if data is poor. the simulated conditions used. Tools to be used This would list out the testing tools or utilities (if any) that are to be used in the project (e. Referenced documents can also be attached here. Deliverables This section contains the various deliverables that are due to the client at various points of time (i. Cognizant Technology Solutions.

such as operational profiles. A system can be configured to fit several business models. as input data has the greatest influence on functional testing and is the simplest to manipulate. Testing is the process of creating. and will show that testing can be improved by a careful choice of input data. Data is a crucial part of most functional testing. the way the test is going to be run and applied. The paper will focus on input data. Configuration data can dictate control flow. which finally spews forth yet more data to be checked against expectations. implementing and evaluating tests. you should design test cases. A business may look to an application's configurability to allow them to keep up with the market without being slowed by the development process. performing a specific set of tests at appropriate points in the process is more important than running the tests at a specific time. A System Is Programmed By Its Data Many modern systems allow tremendous flexibility in the way their basic functionality can be used. presentation and user interface. if you're testing a specific functionality. You must have a consistent schedule for testing. you have to decide such things as what exactly you are testing and testing for. etc. you must know how it's supposed to work. Data describes the initial conditions for a test. You should have a definition of what success and failure are. This will enable the monitoring and testing reports to be co-coordinated with any feedback received. the paper will concentrate most on data-heavy applications. etc. Page 78 ©Copyright 2007. The paper will not consider areas where data is important to non-functional testing. what steps are required. is the medium through which the tester influences the software. Cognizant Technology Solutions. You must understand the limits inherent in the tests themselves. Effective quality control testing requires some basic goals and understanding: You must understand what you are testing. data manipulation. In other words. the more formal a plan the better. All Rights Reserved C3: Protected . massive datasets and environmental tuning. rather than output data or the transitional states the data passes through during processing. forms the input. how the protocols behave. Tests must be planned and thought out a head of time. those which use databases or are heavily influenced by the data they hold. is close enough good enough? You should have a good idea of a methodology for the test.Handout – Software Testing process and the date the test was carried out. an individual may look for a personalized experience from commonly-available software. This paper sets out to illustrate some of the ways that data can influence the test process. work (almost) seamlessly with a variety of cooperative systems and provide tailored experiences to a host of different users. In doing this. extrapolated. summarized and referenced by the functionality under test. Roles of Data in Functional Testing Testing consumes and produces large amounts of data. Data is manipulated.

and varied to allow diagnosis. Identify Who is to Conduct the Tests In order to ensure consistency of the testing process throughout the organization. whether they are good or bad. It should also list the duties of the appointed co-ordinators. This task would normally be carried out by a nominated member of the Business Recovery Team or a member of the Business Continuity Planning Team. They may obscure problems or avoid them altogether. effective reporting. it is hard to communicate problems to coders. and allows tests to be repeated with confidence. Each business process should be thoroughly tested and the coordinator should ensure that each business unit observes the necessary rules associated with ensuring that the testing process is carried out within a realistic environment. Good data allows diagnosis. that take longer to execute. one or more members of the Business Continuity Planning (BCP) Team should be nominated to co-ordinate the testing process within each business unit.Handout – Software Testing Functional Testing Suffers If Data Is Poor Tests with poor data may not describe the business model effectively. Cognizant Technology Solutions. or require lengthy and difficult setup. Poor data tends to result in poor tests. Good data can greatly assist in speedy diagnosis and rapid re-testing. Without this. Page 79 ©Copyright 2007. the tests should be independently monitored. Identify Who is to Control and Monitor the Tests In order to ensure consistency when measuring the results. Good Data Is Vital To Reliable Test Results An important goal of functional testing is to allow the test to be repeated with the same result. All Rights Reserved C3: Protected . A formal test plan is a document that provides and records important information about a test project. they may be hard to maintain. a nominated testing and across the organization. and it can become difficult to have confidence in the QA team's results. Good Data Can Help Testing Stay On Schedule An easily comprehensible and well-understood dataset is a tool to help communication. This section of the BCP should contain the names of the BCP Team members nominated to coordinate the testing process. Regression testing and automated test maintenance can be made speedier and easier by using good data. while an elegantly-chosen dataset can often allow new tests without the overhead of new data. for example: Project and quality assumptions Project background information Resources Schedule & timeline Entry and exit criteria Test milestones Tests to be performed Use cases and/or test cases Criteria for Test Data Collection This section of the Document specifies the description of the test data needed to test recovery of each business process.

All Rights Reserved C3: Protected . It is important that clear instructions are given to the Core Testing Team regarding the simulated conditions which have to be observed. The 'Preparing for a Possible Emergency' Phase of the BCP process will involve the identification and implementation of strategies for back up and recovery of data files or a part of a business process. it is necessary for the core testing team to be trained in the emergency procedures. Prepare Feedback Questionnaires It is vital to receive feedback from the persons managing and participating in each of the tests. Completion of feedback forms should be mandatory for all persons participating in the testing process. This will enable observations and comments to be recorded whilst the event is still fresh in the persons mind. This section of the BCP should contain a template for a Feedback Questionnaire. may require particularly expensive back up strategies to be implemented. It is important that all persons who are likely to be involved with recovering a particular business process in the event of an emergency should participate in the testing process. Prepare Budget for Testing Phase Each phase of the BCP process which incurs a cost requires that a budget be prepared and approved. This section of the BCP should contain a list of the core testing team for each of the business units who will be responsible for coordinating and undertaking the Business Recovery Testing process. This feedback will hopefully enable weaknesses within the Business Recovery Process to be identified and eliminated. Training Core Testing Team for each Business Unit In order for the testing process to proceed smoothly. Cognizant Technology Solutions. Conducting the Tests The tests must be carried out under authentic conditions and all participants must take the process seriously. It will also contain a list of the duties to be undertaken by the monitoring staff. Critical parts of the business process such as the IT systems. The forms should be completed either during the tests (to record a specific issue) or as soon after finishing as practical. It should be mandatory for the management of a business unit to be present when that unit is involved with conducting the tests.Handout – Software Testing This section of the BCP will contain the names of the persons nominated to monitor the testing process throughout the organization. This section of the BCP will contain a list of the testing phase activities and a cost for each. It should be noted whenever part of the costs is already incorporated with the organization’s overall budgeting process. It is inevitable that these back up and recovery processes will involve additional costs. This is probably best handled in a workshop environment and should be presented by the persons responsible for developing the emergency procedures. Where the costs are significant they should be approved separately with a specific detailed budget for the establishment costs and the ongoing maintenance costs. Page 80 ©Copyright 2007.

The testing co-ordination and monitoring will endeavor to ensure that the simulated environments are maintained throughout the testing process. This training may be integrated with the training phase or handled separately. Every part of the procedures included as part of the recovery process is to be tested to ensure validity and relevance. The training should be carefully planned and delivered on a structured basis. This will enable alternative contact routes to be used. in the event of an emergency occurring outside of normal business hours. Training may be delivered either using in-house resources or external resources depending upon available skills and related costs. provide further comment What were the main comments received in the feedback questionnaires Each test should be assessed as fully satisfactory. provides further comment Were simulated conditions reasonably "authentic" . This is particularly important when the procedures are significantly different from those pertaining to normal operations.if not. in a realistic manner. Where. Test Accuracy of Employee and Vendor Emergency Contact Numbers During the testing process the accuracy of employee and vendor emergency contact information is to be re-confirmed.if not. Training Staff in the Business Recovery Process All staff should be trained in the business recovery process. This process must have safety features incorporated to ensure that if one person is not contactable for any reason then this is notified to a nominated controller.if not. provide further comment Was test data representative .if not. The following questions may be appropriate: Were objectives of the Business Recovery Process and the testing process met . All Rights Reserved C3: Protected . This is particularly important for management and key employees who are critical to the success of the recovery process. adequate or requiring further testing. Cognizant Technology Solutions. Assess Test Results Prepare a full assessment of the test results for each business process. a hierarchical process could be used whereby one person contacts five others. a large numberof persons are to be contacted. provide further comment Did the tests proceed without any problems . each critical part of the business recovery process should be fully tested. The training should be assessed to verify that it has achieved its objectives and is relevant for the procedures involved. This activity will usually be handled by the HRM Department or Division. All contact numbers are to be validated for all involved employees. This section of the BCP is to contain a list of each business process with a test schedule and information on the simulated conditions being used. Page 81 ©Copyright 2007.Handout – Software Testing Test each part of the Business Recovery Process In so far as it is practical.

Consideration should also be given to the development of a comprehensive corporate awareness program for communicating the procedures for the business recovery process. Training Materials Development Schedule Once the training needs have been identified it is necessary to specify and develop suitable training materials. Develop Objectives and Scope of Training The objectives and scope of the BCP training activities are to be clearly stated within the plan. and the training fine tuned.Handout – Software Testing Managing the Training Process For the BCP training phase to be successful it has to be both well managed and structured. as appropriate. These manual procedures must be fully understood by the persons who are required to carry them out. Training Needs Assessment The plan must specify which person or group of persons requires which type of training. For example it may be necessary to carry out some process manually if the IT system is down for any length of time. what specific training is required. It is necessary for all new or revised processes to be explained carefully to the staff. This section of the BCP will identify for each business process what type of training is required and which persons or group of persons need to be trained. however. for smaller organizations the training may be better handled in a workshop style. This will enable the training to be consistent and organized in a manner where the results can be measured. Prepare Training Schedule Once it has been agreed who requires training and the training materials have been prepared a detailed training schedule should be drawn up. Cognizant Technology Solutions. an estimate of resources and an estimate of the completion date. Page 82 ©Copyright 2007. All Rights Reserved C3: Protected . it could delay the organization in reaching an adequate level of preparedness. It will be necessary to identify the objective and scope for the training. The BCP should contain a description of the objectives and scope of the training phase. The training will cover all aspects of the Business Recovery activities section of the BCP including IT systems recovery". For larger organizations it may be practical to carry out the training in a classroom environment. This section of the BCP contains information on each of the training programmes with details of the training materials to be developed. The objectives for the training could be as follows : "To train all staff in the particular procedures to be followed during the business recovery process". who needs it and a budget prepared for the additional costs associated with this phase. The scope of the training could be along the following lines: o "The training is to be carried out in a comprehensive and exhaustive manner so that staff become familiar with all aspects of the recovery process. This can be a time consuming task and unless priorities are given to critical training programmes.

The key issues raised by the trainees should be noted and consideration given to whether the findings are critical to the process or not. However. Feedback Questionnaires Assess Feedback Feedback Questionnaires It is vital to receive feedback from the persons managing and participating in each of the training programmes.Handout – Software Testing This section of the BCP contains the overview of the training schedule and the groups of persons receiving the training. A separate communication should be sent to the managers of the business units advising them of the proposed training schedule to be attended by their staff. or the process. have been improved. Completion of feedback forms should be mandatory for all persons participating in the training process. it is necessary to advise them about the training programmes they are scheduled to attend. however well justified. This section of the BCP will contain a format for assessing the training feedback. to be identified and eliminated. The forms should be completed either during the training (to record a specific issue) or as soon after finishing as practical. Each member of staff will be given information on their role and responsibilities applicable in the event of an emergency. This will enable observations and comments to be recorded whilst the event is still fresh in the persons mind. It should be noted whenever part of the costs is already incorporated with the organization’s overall budgeting process. it has to be recognized that. Assessing the Training The individual BCP training programmes and the overall BCP training process should be assessed to ensure its effectiveness and applicability. Identified weaknesses should be notified to the BCP Team Leader and the process strengthened accordingly. Assess Feedback The completed questionnaires from the trainees plus the feedback from the trainers should be assessed. Depending upon the cross charging system employed by the organization. The communication should provide for feedback from the staff member where the training dates given are inconvenient. training incurs additional costs and these should be approved by the appropriate authority within the organization. This section of the BCP contains a draft communication to be sent to each member of staff to advise them about their training schedule. This feedback will enable weaknesses within the Business Recovery Process. If there are a significant number of negative issues raised then consideration should be given to possible retraining once the training materials. All Rights Reserved C3: Protected . This section of the BCP will contain a list of the training phase activities and a cost for each. or the training. Communication to Staff Once the training is arranged to be delivered to the employees. This information will be gathered from the trainers and also the trainees through the completion of feedback questionnaires. This section of the BCP should contain a template for a Feedback Questionnaire for the training phase. Prepare Budget for Training Phase Each phase of the BCP process which incurs a cost requires that a budget be prepared and approved. the training costs will vary greatly. Page 83 ©Copyright 2007. Cognizant Technology Solutions.

The BCP Team Leader will notify the BCP Training Co-ordinator of all approved changes to the BCP in order that the training materials can be updated. Responsibilities for Maintenance of Each Part of the Plan Each part of the plan will be allocated to a member of the BCP Team or a Senior Manager with the organization who will be charged with responsibility for updating and maintaining the plan. Maintaining the BCP It is necessary for the BCP updating process to be properly structured and controlled. Whenever changes are made or proposed to the BCP. Change Controls for Updating the Plan It is recommended that formal change controls are implemented to cover any changes required to the BCP. This section of the BCP contains a draft communication from the BCP Co-ordinator to affected business units and contains information about the changes which require testing or re-testing. An assessment should be made on whether the change necessitates any re-training activities. The BCP Team Leader will remain in overall control of the BCP but business unit heads will need to keep their own sections of the BCP up to date at all times.Handout – Software Testing Keeping the Plan Up-to-date Changes to most organizations occur all the time. Test All Changes to Plan The BCP Team will nominate one or more persons who will be responsible for co-ordinating all the testing processes and for ensuring that all changes to the plan are properly tested. Cognizant Technology Solutions. The increase in technological based processes over the past ten years. Products and services change and also their method of delivery. This will involve the use of formalized change control procedures under the control of the BCP Team Leader. A Change request Form / Change Order form is to be prepared and approved in respect of each proposed change to the BCP. HRM Department will be responsible to ensure that all emergency contact numbers for staff are kept up to date. Advise Person Responsible for BCP Training A member of the BCP Team will be given responsibility for co-ordinating all training activities (BCP Training Co-ordinator). This is necessary due to the level of complexity contained within the BCP. and particularly within the last five. It is important that the relevant BCP coordinator and the Business Recovery Team are kept fully informed regarding any approved changes to the plan. have significantly increased the level of dependency upon the availability of systems and information for the business to function effectively. This chapter deals with updating the plan and the managed process which should be applied to this updating activity. It is necessary for the BCP to keep pace with these changes in order for it to be of use in the event of a disruptive emergency. This section of the BCP will contain a Change Request Form / Change Order to be used for all such changes to the BCP. These changes are likely to continue and probably the only certainty is that the pace of change will continue to increase. the BCP Testing Co-ordinator will be notified. Page 84 ©Copyright 2007. Whenever changes are made to the BCP they are to be fully tested and appropriate amendments should be made to the training materials. The BCP Testing Co-ordinator will then be responsible for notifying all affected units and for arranging for any further testing activities. Similarly. All Rights Reserved C3: Protected .

Cognizant Technology Solutions. Most projects experience these problems at some stage . Furthermore. Page 85 ©Copyright 2007. it may not be time-effective to construct further data to support investigator tests. This can be a symptom of an uncontrolled environment. evidence of the fault is lost. the cost of test maintenance is correspondingly increased. Poor data can make these reports hard to understand. but the original fault is undiagnosed and can carry on into live operation and perhaps future releases. Confusing or over-large datasets can make data selection mistakes more common. testers and business. unrecognized database corruption. or indeed of missing the failure entirely. Each of these groups has different data requirements. Simpler to make test mistakes. the cost increases further. Problems which can be caused by Poor Test Data Most testers are familiar with the problems that can be caused by poor data. the less time spent testing. The BCP Team Leader will notify the BCP Training Co-ordinator of all approved changes to the BCP in order that the training materials can be updated. after further analysis. as the data is restored.recognizing them early can allow their effects to be mitigated. Increased test maintenance cost If each test has its own data. not to be faults at all. Poor data will cause more of these problems. If not spotted at the time of generation. some tests may be excluded from a test run. All Rights Reserved C3: Protected . Everybody makes mistakes. An assessment should be made on whether the change necessitates any re-training activities. It is important to consider inputs and outputs of a process for requirements modeling. Degradation of test data over time Program faults can introduce inconsistency or corruption into a database. Less time spent hunting bugs the more time spent doing unproductive testing or ineffective test maintenance. If that data is itself hard to understand or manipulate. Data can play a significant role in these failures. The following list details the most common problems familiar to the author. If the datasets are poorly constructed. Reduced flexibility in test execution If datasets are large or hard to set up. Larger proportion of problems can be traced to poor data. Inadequate data can lead to ambiguous or incomplete requirements. Confusion between developers. Restoring the data to a clean set gets rid of the symptom. Unreliable test results Running the same test twice produces inconsistent results. A failure to understand each others data can lead to ongoing confusion. A proportion of all failures logged will be found. or of a failure to recognize all the data that is influential on the system. testers stand a greater chance of missing important diagnostic features of a failure.Handout – Software Testing Advise Person Responsible for BCP Training A member of the BCP Team will be given responsibility for co-ordinating all training activities (BCP Training Co-ordinator). Obscure results and bug reports without clearly comprehensible data. they can cause hard-to-diagnose failures that may be apparently unrelated to the original fault. Requirements problems can be hidden in inadequate data. Most reports make reference to the input data and the actual and expected results.

Fixed Input Data Fixed input data is available before the start of the test. The following broad categories allow data to be handled and discussed more easily. Poor database/environment integrity. documents can all be input data. Inability to spot data corruption caused by bugs. and may lend themselves to automated testing / sanity checks. This can make portions of the application untestable for many testers simultaneously. Page 86 ©Copyright 2007. The current date and time can be seen as environmental data. or methods of debt collection from different kinds of customers. If a large number of testers. they can influence and corrupt each others results as they change the data in the system. Although it is perhaps simpler to discuss data in these terms. many references are made to "The Data" or "Data Problems". products. it is useful to split the categorization once more. Business data not representatively tested. It might include a cross reference between country and delivery cost or method. Cognizant Technology Solutions. For the purposes of testing. where new billing products are supported and indeed created by additions to the setup data. it can be hard for the business or the end users to feel confidence in the test effort if they feel distanced from it. Input data Input data is the information input by day-to-day system functions. business can offer new intangible products without developing new functionality .as can be seen in the mobile phone industry. particularly in configuration data. a complex dataset will positively hinder diagnosis. Environmental data Environmental data tells the system about its technical environment. A readily understandable dataset can allow straightforward diagnosis. Small datasets can be manipulated more easily than large datasets. actions. setup data causes different functionality to apply to otherwise similar data. While this may arguably lead to broad testing for a variety of purposes. This can not only cause false results. Setup data Setup data tells the system about the business rules. directory trees and paths and environmental variables. A few well-known datasets can be more easily be checked than a large number of complex datasets. With an effective approach to setup data. Test requirements. and can be seen as part of the test conditions. but can lead to database integrity problems and data corruption. It includes communications addresses. often don't reflect the way the system will be used in practice. it is useful to be able to classify the data according to the way it is used. Accounts. A few datasets are easier to manage than many datasets. or tests.Handout – Software Testing Unwieldy volumes of data. All Rights Reserved C3: Protected . Classification of Test Data Types In the process of testing a system. orders. share the same dataset. Typically.

Organizing the data A key part of any approach to data is the way the data is organized. Typically held in internal system variables. All Rights Reserved C3: Protected . it is temporary and is lost at the end of processing. test handles and instrumentation make it output data). It generally has a correspondence with the input data (cf. This method is most appropriate when used. To sum up. Pair wise. on fixed input data. and so is comprehensive enough to allow a great many new. It allows complete pairwise coverage.which also allows a wide range of tests. adhoc. Database changes will affect it. for non-trivial sets. As such.Handout – Software Testing Consumable Input Data Consumable input data forms the test input It can also be helpful to qualify data after the system has started to use it. reports and database updates. This allows a small. but its state can be inferred from actions that the system has taken. Typically. influenced by the uses that are planned for it. It is most effective when the following conditions are satisfied. Most are also familiar with the ways in which this generally vast set can be cut down. Achieves good test coverage without having to construct massive datasets Page 87 ©Copyright 2007. A subset of the output data is generally compared with the expected results at the end of test execution. reduces data maintenance time and can help improve the test process. during processing of input data. or diagnostic tests. Transitional data is not seen outside the system (arguably. Fortunately. this method of working with fixed input data can help greatly in testing the setup data. This small. this produces a far smaller set of tests than the brute-force approach for all permutations. the test data can contain all possible pairs of permutations in a far smaller set than that which contains all possible permutations. it does not directly influence the quality of the tests. as above. rather than hinders it. permutation helps because: Permutation is familiar from test planning. Good data assists testing. or combinatorial testing addresses this problem by generating a set of tests that allow all possible pairs of combinations to be tested. Cognizant Technology Solutions. Finally. generating tests so that all possible permutations of inputs are tested. and easy to manipulate dataset is capable of supporting many tests. easy to handle dataset . but the data maintenance required will be greatly lessened by the small size of the dataset and the amount of reuse it allows. Permutations Most testers are familiar with the concept of permutation. The same techniques can be applied to test data. Output Data Output data is all the data that a system outputs as a result of processing input data and events. Transitional data Transitional data is data that exists only within the program. but can also include test measurements. the way it is chosen and described. transmissions. A good approach increases data reliability. and includes not only files. Jackson's Structured Programming methodology). these criteria apply to many traditional database-based systems: Fixed input data consists of many rows Fields are independent You want to do many tests without loading / you do not load fixed input data for each test.

Handout – Software Testing
Can perform investigative testing without having to set up more data Reduces the impact of functional/database changes Can be used to test other data - particularly setup data Partitioning Partitions allow data access to be controlled, reducing uncontrolled changes in the data. Partitions can be used independently; data use in one area will have no effect on the results of tests in another. Data can be safely and effectively partitioned by machine / database / application instance, although this partitioning can introduce configuration management problems in software version, machine setup, environmental data and data load/reload. A useful and basic way to start with partitions is to set up, not a single environment for each test or tester, but to set up three shared by many users, so allowing different kinds of data use. These three have the following characteristics: Safe area o Used for enquiry tests, usability tests etc. o No test changes the data, so the area can be trusted. o Many testers can use simultaneously Change Area o o o Used for tests which update/change data. Data must be reset or reloaded after testing. Used by one test/tester at a time.

Scratch area o Used for investigative update tests and those which have unusual requirements. o Existing data cannot be trusted. o Used at tester's own risk! o Testing rarely has the luxury of completely separate environments for each test and each tester. Controlling data, and the access to data, in a system can be fraught. Many different stakeholders have different requirements of the data, but a common requirement is that of exclusive use. While the impact of this requirement should not be underestimated, a number of stakeholders may be able to work with the same environmental data, and to a lesser extent, setup data – and their work may not need to change the environmental or setup data. The test strategy can take advantage of this by disciplined use of text / value fields, allowing the use of 'soft' partitions. 'Soft' partitions allow the data to be split up conceptually, rather than physically. Although testers are able to interfere with each others tests, the team can be educated to avoid each others work. If, for instance, tester 1's tests may only use customers with Russian nationality and tester 2's tests only with French, the two sets of work can operate independently in the same dataset. A safe area could consist of London addresses, the change area Manchester addresses, and the scratch area Bristol addresses. Typically, values in free-text fields are used for soft partitioning.

Page 88 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
Data partitions help because: Allow controlled and reliable data, reducing data corruption / change problems Can reduce the need for exclusive access to environments/machines Clarity Permutation techniques may make data easier to grasp by making the datasets small and commonly used, but we can make our data clearer still by describing each row in its own free text fields, allowing testers to make a simple comparison between the free text (which is generally displayed on output), and actions based on fields which tend not to be directly displayed. Use of free text fields with some correspondence to the internals of the record allows output to be checked more easily. Testers often talk about items of data, referring to them by anthropomorphic personification – that is to say, they give them names. This allows shorthand, but also acts as jargon, excluding those who are not in the know. Setting this data, early on in testing, to have some meaningful value can be very useful, allowing testers to sense check input and output data, and choose appropriate input data for investigative tests. Reports, data extracts and sanity checks can also make use of these; sorting or selecting on a free text field that should have some correspondence with a functional field can help spot problems or eliminate unaffected data. Data is often used to communicate and illustrate problems to coders and to the business. However, there is generally no mandate for outside groups to understand the format or requirements of test data. Giving some meaning to the data that can be referred to directly can help with improving mutual understanding. Clarity helps because: Improves communication within and outside the team Reduces test errors caused by using the wrong data Allows another method way of doing sanity checks for corrupted or inconsistent data Helps when checking data after input Helps in selecting data for investigative tests Data Load and Data Maintenance An important consideration in preparing data for functional testing is the ways in which the data can be loaded into the system, and the possibility and ease of maintenance. Loading the data Data can be loaded into a test system in three general ways. Using the system you're trying to test o The data can be manually entered, or data entry can be automated by using a capture/replay tool.

Page 89 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
o This method can be very slow for large datasets. It uses the system's own validation and insertion methods, and can both be hampered by faults in the system, and help pinpoint them. If the system is working well, data integrity can be ensured by using this method, and internally assigned keys are likely to be effective and consistent. Data can be well-described in test scripts, or constructed and held in flat files. It may, however, be input in an ad-hoc way, which is unlikely to gain the advantages of good data listed above. Data load tools directly manipulate the system's underlying data structures. As they do not use the system's own validation, they can be the only way to get broken data into the system in a consistent fashion. As they do not use the system to load the data, they can provide a convenient workaround to known faults in the system's data load routines. However, they may come up against problems when generating internal keys, and can have problems with data integrity and parent/child relationships. Data loaded can have a range of origins. In some cases, all new data is created for testing. This data may be complete and well specified, but can be hard to generate. A common compromise is to use old data from an existing system, selected for testing, filtered for relevance and duplicates and migrated to the target data format. In some cases, particularly for minor system upgrades, the complete set of live data is loaded into the system, but stripped of personal details for privacy reasons. While this last method may seem complete, it has disadvantages in that the data may not fully support testing, and that the large volume of data may make test results hard to interpret.


Using a data load tool o


Not loaded at all o Some tests simply take whatever is in the system and try to test with it. This can be appropriate where a dataset is known and consistent, or has been set up by a prior round of testing. It can also be appropriate in environments where data cannot be reloaded, such as the live system. However, it can be symptomatic of an uncontrolled approach to data, and is not often desirable. o Environmental data tends to be manually loaded, either at installation or by manipulating environmental or configuration scripts. Large volumes of setup data can often be generated from existing datasets and loaded using a data load tool, while small volumes of setup data often have an associated system maintenance function and can be input using the system.Fixed input data may be generated or migrated and is loaded using any and all of themethods above, while consumable input data is typically listed in test scripts or generated as an input to automation tools. When data is loaded, it can append itself to existing data, overwrite existing data, or delete existing data first. Each is appropriate in different circumstances, and due consideration should be given to the consequences. Testing the Data A theme bought out at the start of this paper was 'A System is Programmed by its Data'. In order to test the system, one must also test the data it is configured with; the environmental and setup data. Environmental data is necessarily different between the test and live environment. Although testing can verify that the environmental variables are being read and used correctly, there is little point in testing their values on a system other than the target system. Environmental data is often checked
Page 90 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

it is important to have a well-known set of fixed input data and consumable input data. and good data can be used as a tool to enable and improve communication throughout the project. as the business environment changes – particularly if there is a long period between requirements gathering and live rollout. All Rights Reserved C3: Protected . Effective testing of setup data is a necessary part of system testing. Setup data can change often. The setup data should be organized to allow a good variety of scenarios to be considered The setup data needs to be able to be loaded and maintained easily and repeatable The business needs to become involved in the data so that their setup for live can be properly tested When testing the setup data.Handout – Software Testing manually on the live system during implementation and rollout. Well-planned data can allow flexibility and help reduce the cost of test maintenance. The advantages of testing the setup data include: Overall testing will be improved if the quality of the setup data improves Problems due to faults in the live setup data will be reduced The business can re-configure the software for new business needs with increased confidence Data-related failures in the live system can be assessed in the light of good data testing Conclusion Data can be influential on the quality of testing. Does the planned/current setup data induce the functionality that the business requires? Will changes made to the setup data have the desired effect? Testing for these two questions only becomes possible when that data is controlled. The following points summarize the actions that can influence the quality of the data and the effectiveness of its usage: Plan the data for maintenance and flexibility Know your data. Aspects of all the elements above come into play. and make its structure and content transparent Use the data to improve understanding throughout testing and the business Test setup data as you would test functionality Page 91 ©Copyright 2007. Common data problems can be avoided or reduced with preparation and automation. This allows the effects of changes made to the setup data to be assessed repeat ably and allows results to be compared. throughout testing. Cognizant Technology Solutions. and the wide variety of possible methods will not be discussed further here. Testing done on the setup data needs to cover two questions.

The documenting of the deviation is describing the conditions. the I/S professional will need to ensure that the information is accurate. The “What should be” shall be called the “Criteria”. The ‘What is”: can be called the statement of condition. questions almost arise. The statement of condition is uncovering and documenting the facts. For those facts. When a deviation is identified between what is found to actually exist and what the user thinks is correct or proper . If a comparison between the two gives little or no practical consequence. which represents what the user desires. These two attributes are the basis for a finding. Identification of the cause is the necessary as a basis for corrective action. the first essential step toward development of a problem statement has occurred. Criteria – Tells what should be.Introduction Test Problem is a condition that exists within the software system that needs to be addressed. as they exist. The actual deviation will be the difference or gap between “what –is” and “ what is desired”. What is a fact? The statement of condition will of course depend on the nature and extent of the evidence or support that is examined and noted. When one or more these attributes is missing. It is difficult to visualize any type of problem that is not in some way characterized by this deviation. These concepts are the first two and the most basic . The statement of condition should document as many of the following attributes as appropriate of the problem. and worded as clearly and precisely as possible. A well developed problem statement will include each of these attributes. as they currently exist. making up the statement of condition.Essentially the user compares” what is” with “what should be”. The following four attributes should be developed for all the test problems: Statement of condition –Tells what it is. All Rights Reserved C3: Protected .Handout – Software Testing Test Logs . Carefully and completely documenting a test problem is the first step in correcting the problem. Effect: Tells why the difference between what is and what should be is significant Cause: Tells the reasons for the deviation. such as Criteria: Why is the current state inadequate? Effect: How significant is it? Cause: What could have cause of the problem? Factors defining the Test Log Generation Document Deviation: Problem statements begin to emerge by process of comparision. well supported. Cognizant Technology Solutions. attributes of a problem statement. Page 92 ©Copyright 2007. and the criteria. no finding exists.

Outputs /Deliverables – The products that are produced from the activity. Users/Customers served –The organization .Handout – Software Testing Activities Involved:. It can be stated in the either negative or positive terms. Work Paper to describe the problem. The Criterion is the user’s statement of what is desired. Inputs . For example . Cognizant Technology Solutions. Deficiencies noted – The status of the results of executing this activity and any appropriate interpretation of those facts. – The specific step-by –step activities that are utilized in producing the output from the identical activities. All Rights Reserved C3: Protected .The specific business or administered activities that are being performed during Test Log generation are as follows: Procedures used to perform work.or class users/customers serviced by this activity. it could indicate the need to reduce the complaints or delays as well as desired processing turn around time.individuvals. For example the following Work paper provides the information for Test Log Documentation: Page 93 ©Copyright 2007.events.or documents that cause this activity to be executed. and document the statement of condition and the statement of criteria.The triggers.

Test Results Data This data will include. This description includes but not limited to : Data the defect uncovered Name of the Defect Location of the Defect Page 94 ©Copyright 2007. Test Suites. Defect This category includes a Description of the individual defects uncovered during the testing process. the validation of which becomes the Test Objective. and Test Events These are the test products produced by the test team to perform testing. Test Transactions. Inspections – A verification of process deliverables against deliverable specifications.Handout – Software Testing Collecting Status Data Four categories of data will be collected during testing. Test factors -The factors incorporated in the plan. Functions/Sub functions . Cognizant Technology Solutions.Validation that data/Objects can be correctly passed among Software components. All Rights Reserved C3: Protected .Identifiable Software components normally associated with the requirements of the software.The hardware and Software environment in which the software system will operate. which will be based on software requirements. Business Objective –The validation that specific business objectives have been met. Test transactions/events: The type of tests that will be conducted during the execution of tests. Units.The smallest identifiable software components Platform. Reviews: Verification that the process deliverables / phases are meeting the user’s true needs. Interface Objectives . These are explained in the following paragraphs.

As described the most common test Report is a simple Spread sheet . Many organizations use spreadsheet package to maintain test results. All Rights Reserved C3: Protected . the test that will be performed to determine the status of that component. The intersection can be coded with a number or symbol to indicate the following: 1=Test is needed. which indicates the project component for which the status is requested. and the software development team. Cognizant Technology Solutions. and when it was entered for retest. Storing Data Collected during Testing It is recommended that a database be established in which to store the results collected during testing. The test reports are for use of testers. but not performed 2=Test currently being performed 3=Minor defect noted 4=Major defect noted 5=Test complete and function is defect free for the criteria included in this test Page 95 ©Copyright 2007. Use of Function/Test matrix: This shows which tests must be performed in order to validate the functions and also used to determine the status of testing. It is also suggested that the database be put in online through client/server systems so that with a vested interest in the status of the project can be readily accessed for the status update. test managers.Handout – Software Testing Severity of the Defect Type of Defect How the defect was uncovered (Test Data/Test Script) The Test Logs should add to this information in the form of where the defect originated . when it was corrected. Developing Test Status Reports Report Software Status Establish a Measurement Team Inventory Existing Project Measures Develop a Consistent Set of Project metrics Define Process Requirements Develop and Implement the Process Monitor the Process The Test process should produce a continuous series of reports that describe the status of testing. and the results of testing at any point of time. The frequency of the test reports should be based on the discretion of the team and extensiveness of the test process.

Word –Processing: One way of increasing the utility of computers and word processors for the teaching of writing may be to use software that will guide the processes of generating. Some Database test tools like Data Vision is a database reporting tool similar to Crystal Reports.'' GRG . Cognos is looking into what interest people have in the product to assess what their strategy should be with respect to the Linux ``market. Some query tools available for Linux based databases include: MySQL dbMetrix PgAccess Cognos Powerhouse This is not yet available for Linux. From the LaTeX2e and DocBook output files you can in turn produce PDF. you can quickly scan through any number of these reports and see how each person's history compares. order entry systems. XML.or comma-separated text files. however.Use of word processing. and data base management products.Handout – Software Testing Methods of Test Reporting Reporting Tools . Status Report Word Processing Tests or Keypad Tests Basic Skills Tests or Data Entry Tests Progress Graph Game Scores Test Report for each test Page 96 ©Copyright 2007. or tab. This allows each person to use the normal functions of the computer keyboard that are common to all word processors. Reports can be viewed and printed from the application or output as HTML. text. organizing. email editors. A one-page summary report may be printed with either the Report Manager program or from the individual keyboard or keypad software at any time. defect tracking. PostScript. Individual Reports include all of the following information. PostScript.GNU Report Generator The GRG program reads record and field information from a dBase3+ file. HTML. The program was loosely designed to produce TeX/LaTeX formatted output. Cognizant Technology Solutions. troff. LaTeX2e. but plain ASCII text. delimited ASCII text file or a SQL query to a RDBMS and produces a report listing. HTML or any other kind of ASCII based output format can be produced just as easily. and more. database. All Rights Reserved C3: Protected . and graphic tools to prepare test reports. DocBook. composing and revising text. From the Report Manager.

developers. Cognizant Technology Solutions. The following measurements generated during testing are applicable: o Total number of tests o Number of Tests executed to date o Number of tests executed successfully to date o Data concerning software defects include o Total number of defects corrected in each activity o Total number of defects entered in each activity. Testing Data used for metrics Testers are typically responsible for reporting their test status at regular intervals. test execution progress. which can be repeated throughout the application life cycle Provides Analysis and Decision Support Graphs and reports help analyze application readiness at any point in the testing process Requirements coverage.Defining the components that should be included in a test report.Ability to draw statistically valid conclusions from quantitative test results.Handout – Software Testing Test Director: Facilitates consistent and repetitive testing process Central repository for all testing assets facilitates the adoption of a more consistent testing process. defect statistics can be used for production planning Provides Anytime. Anywhere access to Test Assets Using Test Director’s web interface. business analysts and Client can participate and contribute to the testing process Traceability throughout the testing process Test Cases can be mapped to requirements providing adequate visibility over the test coverage of requirements Test Director links requirements to test cases and test cases to defects Manages Both Manual and Automated Testing Test Director can manage both manual and automated tests (Win Runner) Scheduling of automated tests can be effectively done using Test Director Test Report Standards . All Rights Reserved C3: Protected . Statistical Analysis . run schedules. o Average duration between defect detection and defect correction o Average effort to correct a defect o Total number of defects remaining at delivery o Software performance data us usually generated during system testing. tester. o Average CPU utilization o Average memory Utilization o Measured I/O transaction rate Page 97 ©Copyright 2007. once the software has been integrated and functional testing is complete.

as paper report will summarize the data.Handout – Software Testing Test Reporting A final test report should be prepared at the conclusion of each test activity. Integration Test Report Integration testing tests the interfaces between individual projects. A good test plan will identify the interfaces and institute test conditions that will validate interfaces.Purpose of a Test Report: The test report has one immediate and three long term purposes. The test report can be a combination of electronic data and hard copy. The Third long term purpose is to show what was accomplished in case of an Y2K lawsuit. Cognizant Technology Solutions. The second long term purpose is to use the data to analyze the rework process for making changes to prevent the defects from occurring in the future. Given is the Individual Project test report except that conditions tested are interfaces.9 . Individual Project Test Report These reports focus on the Individual projects(software system). there is no reason to print that. Page 98 ©Copyright 2007. Knowing which functions have been correctly tested and which ones still contain defects can assist in taking corrective actions. draws appropriate conclusions and present recommendations. This includes the following Individual Project Test Report Integration Test Report System Test Report Acceptance test Report These test reports are designed to document the results of testing as defined in the testplan. to assess the potential consequences and initiate appropriate actions to minimize those consequences. could eliminate or minimize the occurrence of high frequency defects. All Rights Reserved C3: Protected . The first of the three long term uses is for the project to trace problems in the event the application malfunctions in production. The immediate purpose is to provide information to customers of the software system so that they can determine whether the system is ready for production . they should prepare a report on their results. These defect prone components identify tasks/steps that if improved.when different testers should test individual projects. if the function matrix is maintained electronically. and if so. For example.

could eliminate or minimize the occurrence of high frequency defects in future. If these details are maintained Electronically . Knowing which functions have been correctly tested and which ones still contain defects can assist in taking corrective actions. Page 99 ©Copyright 2007. The second objective is to ensure that software system can operate in the real world user environment. One Long term objective is for the Project and the other is for the information technology function. not included in the report. changing business conditions. and when tests should occur. If the defined requirements are those true needs. Cognizant Technology Solutions. The Acceptance Test Report should encompass these criteria’s for the User acceptance respectively. All Rights Reserved C3: Protected . testing should have accomplished this objective. The project can use the test report to trace problems in the event the application malfunction in production. which includes people skills and attitudes. and so forth. Conclusion The Test Logs obtained from the execution of the test results and finally the test reports should be designed to accomplish the following objectives: Provide Information to the customer whether the system should be placed into production. time pressures. then it need only be referenced . The system test Report should present the results of executing the test plan. what was to be tested. if so the potential consequences and appropriate actions to minimize these consequences. Acceptance Test Report There are two primary objectives of Acceptance testing Report: The first is to ensure that the system as implemented meets the real operating needs of the user/customer. These defect prone components identify tasks/steps that if improved. how was it to be tested. The data can also be used to analyze the developmental process to make changes to prevent defects from occurring in the future.Handout – Software Testing System Test Reports A System Test plan standard that identified the objective of testing .

. Goals The goals of a test case is to automate or document the following: Perform a single test (e. All Rights Reserved C3: Protected . Cognizant Technology Solutions..g. Help developers improve the quality of the specifications (e. use case path and class responsibilities) of the item under test. the type of failures to be elicited). Help improve the quality of the item under test. Document the producer of the test case..g. the objectives of a single test case include: Document the purpose of the test case (i. Help developers understand the behavior of the item under test. the part of the item under test being tested. Objectives To support these goals. Cause failures that uncover underlying defects so that they can be identified and removed.Handout – Software Testing Test Report A Test Report is a document that is prepared once the testing of a software product is complete and the delivery is to be made to the customer.e. a single test of a use case path or class method). Contents of a Test Report The contents of a test report are as follows: Executive Summary Overview Application Overview Testing Scope Test Details Test Approach Types of testing conducted Test Environment Tools Used Metrics Test Results Test Deliverables Recommendations Test Case A test case is a testing work product that automatically performs a single test on an executable work product. Page 100 ©Copyright 2007. This document would contain a summary of the entire project and would have to be presented in a way that any person who has not worked on the project would also get a good overview of the testing effort.

e. All Rights Reserved C3: Protected . The Integration Team for integration test cases.. exceptions raised. thereby supporting regression testing. and the collaborators of the item under test into their correct pretest states. Benefits A test case provides the following benefits: Automates a single test..e. Cognizant Technology Solutions. o The Software Development Team for design model and unit test cases.. send it test messages. postconditions) to the expected responses to identify failures that imply the existence of defects in the item under test. Compare the actual responses (i.g.. Contents Test case objectives Test preparation (e. o The Architecture Team for architecture model test cases. test oracle) Test reporting script Test finalization script Stakeholders Producers: o o o o o The Requirements Team for requirements model test cases.e. changes in state and messages sent) to the test stimuli. Documents test results Failure to produce test cases increases the probability that the item under test will contain defects that will make the application fail to meet its requirements. Maintainers: o The Requirements Team for requirements model test cases. values returned.. Failure to automate test cases makes regression testing more expensive and less likely to occur. The Architecture Team for architecture model test cases. Evaluator: Test Inspection Team Approvers: None. Page 101 ©Copyright 2007.. Stimulate the item (e.g. to place objects under test into the appropriate pre-test states) Test stimuli (e. and provide the necessary test data). the test stimuli. to send test messages or raise test exceptions) Expected behavior (i. oracle. Documents a single test in terms of objective. raise test exceptions). place the item under test.g. Report the results of the associated test.g. The Independent Test Team for system test cases. etc. Observe how the item responds (e.Handout – Software Testing Prepare the item under test for testing (i. The SoftwareDevelopment Team for design model and unit test cases..

The relevant item under test is started. The Test Team for performing system testing. architecture. method signatures. All Rights Reserved C3: Protected . The Independent Test Team for system test cases. or design are completed. Domain object model The Architecture Team for: 1). The relevant requirements. The relevant team is staffed. The relevant test suite is started.. Unit testing of the software components 3). branching and looping logic) Stakeholders: None Page 102 ©Copyright 2007. The Integration Team for performing integration testing. o o Phases Initiation: Completed Construction: Completed Delivery: Completed Usage: Maintained Retirement: Archived Preconditions A test case typically can be started if the following preconditions hold: The relevant sections of the Project Test Plan are completed. Inputs Work products: Project Test Plan System Requirements Specification System Architecture Document Software Architecture Document Javadoc including responsibilities Software components (e. Use case model 2). The Integration Team for integration test cases. assertions.Handout – Software Testing o o Users: o Tumultuous 1). Model testing of the software design 2). Unit testing of the software architecture prototype The SoftwareDevelopment Team for 1). Cognizant Technology Solutions.g. Model testing of the software architecture 2). 4).

Network.) Features to test with priority/criticality. and the test case developer can make mistakes. A test case has set of test inputs. A series of test data that is logically tested together is a. Test Deliverables. Test Log d. test cases need to be evaluated for defects. All Rights Reserved C3: Protected . Thus. Test Strategy/Approach based on customer priorities. Communication etc. and system testing). execution conditions and expected results. To support regression testing. Test harness 2). Test Script Answers: 1) c 2) c Page 103 ©Copyright 2007. The document that describes the expected output as well as inputs is a. Test Plan c. A test reflects what tests need to be performed. test cases will be automated whenever practical. Software. Test cases do not document the results of the tests. then it will be difficult to know if the defect causing the failure is in the item under test or in the test case.. Test Case d. If the quality of the test cases is not at least as good as the quality of the item under test. Test Specification b. Test Case b. unit testing.Handout – Software Testing Guidelines Test cases will be used at all levels of testing (e.g. Cognizant Technology Solutions. Test Environment (Hardware. The oracle can be incorrect. Test cases need not document how to perform the test unless they are automated. which are documented in the associated test report. Test Result c. Test your Understanding 1). When performed manually. this information is documented in the associated test procedure. model testing. integration testing. Guidelines A test case is constrained by the following conventions: Content and Format Standard Inspection Checklist SUMMARY A test plan contains description of testing objectives and Goals.

So in this context defects are identified as any failure to meet the system requirements. you will be able to: Describe defect lifecycle. and reporting What is a Defect? A mismatch in the application and its specification is a defect. The actual data about defect rates are then fit to the model. This evaluation is described as system reliability growth modelling. Symptoms (flaws) of faults contained in software that is sufficiently mature for production will be considered as defects. A software error is present when the program does not do what its end user expects it to do. A Defect is a product anomaly or flaw. Quality is the indication of how well the system meets the requirements. Such an evaluation estimates the current system reliability and predicts how the reliability will grow if testing and defect removal continue. Rigorous evaluation uses assumptions about the arrival or discovery rates of defects during the testing process. tracking. Defects include such things as omissions and imperfections found during testing phases. An evaluation of defects discovered during testing provides the best indication of software quality. Cognizant Technology Solutions. A deviation from expectation that is to be tracked and resolved is also termed a defect.Handout – Software Testing Chapter 7: Defect Management Learning Objective After completing this chapter. All Rights Reserved C3: Protected . Defect Classification The severity of bugs will be classified as follows: Page 104 ©Copyright 2007. Defect evaluation is based on methods that range from simple number count to rigorous statistical modeling.

the easier it will be for the developers to determine the problem and fix it. When you are reporting a defect the more information you supply. All Rights Reserved C3: Protected . Simple problems can have a simple report. Supply a copy of all relevant reports and data including copies of the expected results. but the more complex the problem– the more information the developer is going to need. Page 105 ©Copyright 2007. project and data used. Summarize what you think the problem is. how to get it and what needs to be changed.Handout – Software Testing Defect Lifecycle Defect Reporting and Tracking The key to making a good report is providing the development staff with as much information as necessary to reproduce the bug. This can be broken down into 5 points: Give a brief description of the problem List the steps that are needed to reproduce the bug or problem Supply all relevant information such as version. Cognizant Technology Solutions. For example: cosmetic errors may only require a brief description of the screen.

The report should explain exactly how to reproduce the problem and an explanation of exactly what the problem is. such as: The name of the process and how to get to it. If you have to enter any data. Include all proper menu names. If specific data is involved. they need to know which version to use when testing out the bug. All Rights Reserved C3: Protected . This includes spread sheets. such as a cosmetic error on a screen. you should include two versions of the dataset. Steps: List the steps taken to recreate the bug. Documentation on what was expected. In most cases the more information/ correct information given the better. (Expected results) The source of the expected results. As a rule the detail of your report will increase based on The severity of the bug. The level of the processing. If the dataset from before the process is not included. Go through the process again and see if there are any steps that can be removed. (Perceived results) An explanation of how the results differed. In either case. list them. one before the process and one after. Cognizant Technology Solutions. if available. In most cases the product is not static. don’t abbreviate and don’t assume anything.Handout – Software Testing However. Anatomy of a bug report Bug reports need to do more than just describe the bug. When you report the steps they should be the clearest steps to recreating the bug. an earlier version of the software and any formulas used) Documentation on what actually happened. The complexity of reproducing the bug. developers can trace what is happening. developers will be forced to try and find the bug based on forensic evidence. you should include a dataset that exhibits the error. Data: Unless you are reporting something very simple. a copy of the data both before and after the process should be included. Page 106 ©Copyright 2007. If there are parameters. The basic items in a report are as follows: Version: This is very important. supply the exact data entered. an error in processing will require a more detailed description. Copies of any output should be included. After you’ve finished writing down the steps. If you’re reporting a processing error. They have to give developers something to work with so that they can successfully reproduce the problem. With the data. Identify the individual items that are wrong. developers will have been working on it and if they’ve found a bug– it may already have been reported or even fixed. Product: If you are developing more than one product– Identify the product in question.make sure you’ve included everything you type and do to get to the problem. follow them .

including the version number. Testers will need this information for later regression testing and verification. In order to work it must supply all necessary information to not only identify the problem but what is needed to fix it as well. On re-testing the defect. include the version number and the dataset used) This information should be stored in a centralized location so that Developers and Testers have access to the information. it must be reported to development so that it can be fixed. It should include information about the product. but detail what is wrong. Duplicate – The bug has already been reported. which will follow the same cycle as an open defect. Invalid Bug – The reported bug is not valid one as per the requirements/design As Designed – This is an intended functionality as per the requirements/design Deferred –This will be an enhancement. Document – Once it is set to any of the above statuses apart from Open. Once the development team has started working on the defect the status is set to WIP ((Work in Progress) or if the development team is waiting for a go ahead or some technical feedback. Defect Tracking After a defect has been found. and the defect still exists. If you have a report to compare against. it is set to Closed. they will set to Dev Waiting. SUMMARY A bug report is a case against a product. Include what you expected. Cognizant Technology Solutions. identify it and fix it. After the development team has fixed the defect. Page 107 ©Copyright 2007. include it and its source information (if it’s a printout from a previous version. The Project Lead of the development team will review the defect and set it to one of the following statuses: o o o o o o Open – Accepts the bug and assigns it to a developer. Include a list of what was expected. It is not enough to say that something is wrong. Remember report one problem at a time. the status is set to FIXED. supply documentation. what data was used. The Initial State of a defect will be ‘New’. The developers need it to reproduce the bug. If the fixed defect satisfies the requirements/passes the test case. Supporting documentation: If available.Try to weed out any extraneous information.Handout – Software Testing Description: Explain what is wrong . The report should be written in clear concise steps. The report must also say what the system should be doing. so that someone who has never seen the system can follow the steps and reproduce the problem. If the process is a report. don’t combine bugs in one report. the status is set to REOPENED. include a copy of the report with the problem areas highlighted. which means the defect is ready to re-test. and the testing team does not agree with the development team it is set to document status. All Rights Reserved C3: Protected .

Logging a defect b. All Rights Reserved C3: Protected . The following is NOT a defect management activity a. Unexpected error/event that needs investigation c. All the above 2). Tracking a defect to closure c.Handout – Software Testing Test your Understanding 1). Cognizant Technology Solutions. Preventing defects Answers: 1) a&b 2) c Page 108 ©Copyright 2007. Defect is defined as a. Temporary problem that is not related to the software d. Software problem that requires corrective action b. Finding the person who introduced the defect d.

This required a large staff of test personnel to perform expensive. It is necessary to ensure that these systems are reliable. testing is a repetitive activity. Reducing Testing Costs The cost of performing manual testing is prohibitive when compared to automated methods.Handout – Software Testing Chapter 8: Automation Learning Objective After completing this chapter. some types of testing. Automation Benefits Today. All Rights Reserved C3: Protected . and with fewer errors than individuals. and have the ability to support business processes. you will be able to: Explain automated testing What is Automation? Automated testing is automating the manual testing process currently in use. but several reasons are common across industries. Page 109 ©Copyright 2007. allowing tests to be completed many times faster than the fastest individual. Owing to the size and complexity of today’s advanced software applications. they remain repetitious throughout the development lifecycle. Many internal and external factors are forcing organizations to ensure a high level of software quality and reliability. load/stress testing using automated methods require only a fraction of the computer hardware that would be necessary to complete a manual test. Automation allows the tester to reduce or eliminate the required “think time” or “read time” necessary for the manual interpretation of when or where to click the mouse or press the enter key. As more organizations develop mission-critical systems to support their business activities. An automated test executes the next operation in the test hierarchy at machine speed. Automation of testing processes allows machines to complete the tedious. The reason is that computers can execute instructions many times faster. such as load/stress testing. and time-consuming manual test procedures. rigorous application testing is a critical part of virtually all software development projects. In the past. manual testing is no longer a viable option for most testing situations. The very nature of application software development dictates that no matter which methods are employed to carry out testing (manual or automated). Cognizant Technology Solutions. Furthermore. Therefore. most software tests were performed using manual methods. Every organization has unique reasons for automating software quality activities. repetitive work while human personnel perform other tasks. built according to specification. Using Testing Effectively By definition. are virtually impossible to perform manually. Imagine performing a load test on a typical distributed client/server application on which 50 concurrent users were planned. Many automated testing tools can replicate the activity of a large number of users (and their associated transactions) using a single computer. the need is greatly increased for testing methods that support business objectives.

the entire test operation could be created on a single machine having the ability to run and rerun the test as necessary. When applications need to be deployed across different hardware or software platforms. an available network. the tester has a very high degree of control over which types of tests are being performed. Cognizant Technology Solutions. As another example. Replicating Testing Across Different Platforms Automation allows the testing organization to perform consistent and repeatable tests. organizations are required to comply with strict quality regulations as well as being required to document their quality assurance efforts for all parts of their systems. standard or benchmark tests can be created and repeated on target platforms to ensure that new platforms operate consistently. and a cadre of coordinators to relay instructions to the users would be required. Using automated tests enforces consistent procedures that allow developers to evaluate the effect of various application modifications as well as the effect of various user actions. It is easy to see why manual methods for load/stress testing is an expensive and logistical nightmare. at night or on weekends without having to assemble an army of end users. and how the tests will be executed.Handout – Software Testing To do the testing manually. 50 application users employing 50 PCs with associated software. Most importantly. All Rights Reserved C3: Protected . For example. imagine the same application used by hundreds or thousands of users. Greater Application Coverage The productivity gains delivered by automated testing allow and encourage organizations to test more often and more completely. With an automated scenario. In some industries such as healthcare and pharmaceuticals. Repeatability and Control By using automated techniques. Page 110 ©Copyright 2007. automated tests can be executed as many times as necessary without requiring a user to recreate a test script each time the test is run. automated tests can be built that extract variable data from external files or applications and then run a test using the data as an input value. Greater application test coverage also reduces the risk of exposing users to malfunctioning or non-compliant software.

but not all.Automated testing can be used to verify the performance of application paths that are used with a high degree of frequency when the software is running in full production. All Rights Reserved C3: Protected . invoicing and other high volume activities where software failures would occur frequently. Examples include: creating customer records. it is also a prime candidate for automation. This modular approach saves time and money when compared to creating a new end-to-end script for each and every test. common outline files can be created to establish a testing session. Page 111 ©Copyright 2007. types of tests can be automated. If the application fails. software applications can literally define or control the core of a company’s business. the company can face extreme disruptions in critical operations. and tests that require constant human intervention are usually not worth the investment to automate. For example.Most.If a testing procedure can be reused many times. Critical Business Processes . Cognizant Technology Solutions. The following are examples of criteria that can be used to identify tests that are prime candidates for automation. Repetitive Testing . tests that run only once. These automated modules can be used again and again without having to rebuild the test scripts. close a testing session and apply testing values. High Path Frequency . Examples include: financial month-end closings. sales order entry and other core activities. Mission-critical processes are prime candidates for automated testing.In many situations. Certain types of tests like user comprehension tests. production planning.Handout – Software Testing Automation Life Cycle Identifying Tests Requiring Automation . Any application with a high-degree of risk associated with a failure is a good candidate for test automation.

an automated test should be able to link business requirements to test results. easy-to-modify tests. Ease of Use Testing tools should be engineered to be usable by non-programmers and application endusers. Internet/Intranet Testing A good tool will have the ability to support testing within the scope of a web browser. the testing tool itself should have a short learning curve.Handout – Software Testing Applications with a Long Life Span . What to Look For in a Testing Tool Choosing an automated software testing tool is an important step. Here are several key issues. the greater the benefits are from automation. a testing tool that requires programming skills is unusable by most organizations. Test components built for performing functional tests should also support other types of testing including regression and load/stress testing. Even if programmers are responsible for testing. Test Planning and Management A robust testing tool should have the capability to manage the testing process. GUI and Client/Server Testing A robust testing tool should support testing with a variety of user interfaces and create simple-to manage. The tests created for testing Internet or intranet-based applications should be portable across browsers. Test component reusability should be a cornerstone of the product architecture. A robust tool will allow users to integrate existing test results into an automated test plan. Cognizant Technology Solutions. Load and Performance Testing The selected testing solution should allow users to perform meaningful load and performance tests to accurately measure system performance. With much of the testing responsibility shifting from the development staff to the departmental level. User training and experience gained in performing one testing task should be transferable to other testing tasks. and one which often poses enterprise-wide implications. It should also provide test results in an easy-tounderstand reporting format. easy-to-understand language. the architecture of the testing tool environment should be open to support interaction with other technologies such as defect or bug tracking packages.If an application is planned to be in production for a long period of time. and should automatically adjust for different load times and performance levels. Page 112 ©Copyright 2007. allowing users to evaluate application readiness based upon the application's ability to support the business requirements. Testing Product Integration Testing tools should provide tightly integrated modules that support test component reusability. Also. and create meaningful end-user and management reports. Finally. provide organization for testing components. which should be addressed when selecting an application testing solution. It should also allow users to include non-automated testing procedures within automated test plans and test results. All products within the testing product environment should be based upon a common. All Rights Reserved C3: Protected .

Document the technical environment needed to execute the tests. Make sure that other groups that might share these resources are informed of this schedule. the test environment can be prepared. Restoration Procedures . Creating a Test Plan For the greatest return on automated testing. those evaluating test automation should consider these fundamental planning steps.Outline the procedures necessary to install the application software to be tested. By doing this.Identify the times during which your testing facilities will be used for a given test. defines the high-level.Identify any support needed from other parts of your organization. Test Schedule . The time invested in detailed planning significantly improves the benefits resulting from test automation. To guarantee the best possible result from an automated testing program. All Rights Reserved C3: Protected . The test environment includes initial set up and description of the environment. a business requirement for a payroll application might be to calculate a salary. Description . a testing plan should be created at the same time the software application requirements are defined. Operational Support . For example. locate and configure test-related hardware and software products and coordinate the human resources required to complete all testing. functional requirements of the software system in question. the software development team.Handout – Software Testing Test Environment Setup Once the test cases have been created. This plan is very much a “living document” that should evolve as the application functions become more clearly defined. These business requirements should be defined in such a way as to make it abundantly clear that the software system correctly (or incorrectly) performs the necessary business functions. The test environment is defined as the complete set of steps necessary to execute the test as described in the test plan. Evaluating Business Requirements Begin the automated testing process by defining exactly what tasks your application software should accomplish in terms of the actual business activities of the end-user.Finally. all user groups and the Page 113 ©Copyright 2007. A good testing plan should be reviewed and approved by the test team. and the procedures needed for installation and restoration of the environment. Installation Procedures . or business requirements. outline those procedures needed to restore the test environment to its original state. Cognizant Technology Solutions. The definition of these tasks. This enables the testing team to define the tests. you are ready to re-execute tests or prepare for a different set of tests. Inputs to the Test Environment Preparation Process Technical Environment Descriptions Approved Test Plan Test Execution Schedules Resource Allocation Schedule Application Software to be installed Test Planning Careful planning is the key to any successful process. or to print a salary check.

and therefore the ultimate success of the test.What critical actions must the application accomplish before it can be deployed? This information forms the basis for making informed decisions on whether or not the application is ready to deploy.Each test case must have a unique name. the standardized test cases can be created that will be used to test the application.Document all screen identifier(s) and expected value(s) that must be verified as part of the test. Inputs to the Test Planning Process Application Requirements .Handout – Software Testing organization’s management. so that the results of these test elements can be traced and analyzed.Identify set up or testing criteria that must be established before a test can be successfully executed. if necessary. Test Case Prerequisites .When is the scheduled release? When are updates or enhancements planned? Are there any specific events or actions that are dependent upon the application? Acceptance Criteria for implementation . Cognizant Technology Solutions. and the expected application values for the procedure being tested. Test Data Sources . Application Implementation Schedules . the procedures for applying those inputs. A proper test case will include the following key components: Test Case Name(s) . run orders and dependencies that might exist between test cases.What is the application intended to do? These should be stated in the terms of the business requirements of the end users. Test Design and Development After the test components have been defined. A test case identifies the specific input values that will be sent to the application. The following items detail the input and output components of the test planning process. Expected Results . Test Case Execution Order . All Rights Reserved C3: Protected . Test Procedures – Identify the application steps necessary to complete the test case. the action to be completed. Page 114 ©Copyright 2007. These expected results will be used to measure the acceptance criteria. Input Values .Take note of the sources for extracting test data if it is not included in the test case. The type and number of test cases needed will be dictated by the testing plan.This section of the test case identifies the values to be supplied to the application as input including.Specify any relationships.

Activities within the test execution are logged and analyzed as follows: Actual Results achieved during test execution are compared to expected application behavior from the test cases Test Case completion status (Pass/Fail) Actual results of the behavior of the technical test environment Deviations taken from the test plan or test process Inputs to the Test Execution Process Approved Test Plan Documented Test Cases Stabilized. repeatable. and validates those results against expected performance. test execution environment Standardized Test Logging Procedures Outputs from the Test Execution Process Test Execution Log(s) Restored test environment Page 115 ©Copyright 2007. This step applies the test cases identified by the test plan. test execution and restoration Executing the Test The test is now ready to be run.Handout – Software Testing Inputs to the Test Design and Construction Process Test Case Documentation Standards Test Case Naming Standards Approved Test Plan Business Process Documentation Business Process Flow Test Data sources Outputs from the Test Design and Construction Process Revised Test Plan Test Procedures for each Test Case Test Case(s) for each application function described in the test plan Procedures for test set up. All Rights Reserved C3: Protected . documents the results. Specific performance measurements of the test execution phase include: Application of Test Cases – The test cases previously created are applied to the target software application as described in the testing environment Documentation . Cognizant Technology Solutions.

Additionally.The Log Review compiles a listing of the activities of all test cases. including application processes that need to be analyzed further. The secret to a controlled test execution is comprehensive planning. Specific elements to be measured and analyzed include: Test Execution Log Review . This step of the process can range from very chaotic to very simple and schedule driven. test automation can offer a dramatic increase in productivity. Application Defects . The problems experienced in test execution are usually attributed to not properly performing steps from earlier in the process. Without an adequate test plan in place to control your entire test process. Phase II: Tool Implementation Preparation Execution Page 116 ©Copyright 2007. noting those that passed. the type of test.This final and very important report identifies potential defects in the software.This summary identifies the total number of tests that were executed. The first and most important step in the process is acquiring a tool that is suitable for your application. Measuring the Results This step evaluates the results of the test as compared to the acceptance criteria set down in the test plan. and a separate test execution cycle may be required for the stress/volume testing of the same application. provide an objective selection of the best tool(s). for example: ready for release. needs more testing. you may inadvertently cause problems for subsequent testing. and the completion status. failed or were not executed. operating environment.Handout – Software Testing The test execution phase of your software test process will control how the test gets applied to the application. Other Phases in Automation Phase I: Tool Acquisition Assessment Evaluation/Selection Installation With the right tool. For example. Determine Application Status . a test execution may be required for the functional testing of an application. Cognizant Technology Solutions. etc. and test team. An automation assessment allows us to evaluate your tool needs. All Rights Reserved C3: Protected . and install and configure the tool(s) for your application and environment. A complete and thorough test plan will identify this need and many of the test cases can be used for both test cycles. Test Execution Statistics .This step identifies the overall status of the application after testing. there may be several test execution cycles necessary to complete all the necessary types of testing required for your application.

Analysis the results via Test manager or in the logs. playback options. and automate tests. it is how you use it that counts. design the test cases. reusable automated test environment. if the system functionality changes. and execute the tests. and it is possible for engineers to edit and maintain such scripts. As with any tool. This is applicable when large volume and different sets of data need to be fed to the application and tested for correctness. During the implementation phase. All Rights Reserved C3: Protected . Tools like Winrunner provide a scripting language. The short-comings of Capture/Playback are that in many cases. The benefit of this approach is that the captured session can be re-run at some later point in time to ensure that the system performs the required behavior. design. the capture/playback session will need to be completely re-run to capture the new sequence of user interactions. Cognizant Technology Solutions. it takes time to define. Page 117 ©Copyright 2007. Select the script that needs to be executed and run it… Wait until execution is done.Handout – Software Testing Selecting the right test tool is only the beginning of a successful test automation effort. however overall savings is usually minimal. we will prepare the test environment. Data Driven Approach Data driven approach is a test that plays back the same user actions but with varying input values. These sequences are played back during the test execution. develop the automated scripts. necessary data table or data pool updation needs to be taken care. Automation Methods Capture/Playback Approach The Capture/Playback tools capture the sequence of manual operations in a test script that are entered by the test engineer. Testing can be done with both positive and negative approach simultaneously. Prerequisite for running the scripts such as tool settings. Test environment /application to be tested to be installed in the machine. The benefit of this approach is that the time consumed is less and accurate than manually testing it. Steps to be followed before execution of scripts: Test tool to be installed in the machine. Scripts need to be reviewed and validated for results and accepted as functioning as expected before they are used live. Although test automation tools can save time through unattended execution. Test Script execution: In this phase we execute the scripts that are already created. This process will result in a robust. This sometimes reduces the effort over the completely manual approach. This allows one script to test multiple sets of positive data.

The following tool vendors evaluated are Compuware. Cognizant Technology Solutions. All Rights Reserved C3: Protected . performance testing and analysis. This appendix evaluates major tool vendors on their test tool characteristics. 4 = This is only supported by use of an API call or third party add-in but not included in the general test tool/below average. tool integration capability. which in turn will dictate how automation will be invoked to support the process. 3 = Basic/ support only. Usually the lower the score the better but this is subjective and is based on the experience of the author and the test professionals opinions used to create this document. The best tool for any particular situation depends on the system engineering environment that applies and the testing methodology that will be used. and Segue. test execution capability.Handout – Software Testing Test script execution process: Automation tool comparison Anyone who has contemplated the implementation of an automated test tool has quickly realized the wide variety of options on the market in terms of both the kinds of test tools being offered and the number of vendors. 5 = No support. Page 118 ©Copyright 2007. Rational. 2 = Good support but lacking or another tool provides more effective support. Mercury. Empirix/RSW. test reporting capability. and vendor qualification. In general a set of criteria can be built up by using this matrix and an indicative score obtained to help in the evaluation process. 1 = Excellent support for this functionality. Functional Test Tool Matrix The Tool Matrix is provided for quick and easy reference to the capabilities of the test tools. Each category in the matrix is given a rating of 1 – 5.

Oracle. databases. Sybase. etc. the applications and so on but on the web it is far different. ODBC and how they hold returned data e. various platforms for browsers. etc changes) fail? How easy is it to read the recorded script. DOM. Web site maps and links. As such. Cognizant Technology Solutions. Ingres. does it contain data. connect using MAC. etc all of them support a universal query language known as SQL and a protocol for communicating with these databases called ODBC (JDBC can be used on java environments). They will speak different languages. they may be disabled. DB2. etc. However this should be done as a minimum in the evaluation process because if the tool of choice cannot recognize the applications objects then the automation process will be a very tedious experience. this is the first thing that most test professionals will do. So the cost to set up a test environment is usually greater than for a client server test where the environment is fairly well defined. Does the tool support low-level recording (mouse drags. SQLServer. Because of the many databases available e.g. will have fast connections and slow connections.g.g. Record and Playback This category details how easy it is to record & playback a test. When automating. How does the tool manipulate this returned data? Can it call stored procedures and supply required input variables? What is the range of functions supplied for this testing? Page 119 ©Copyright 2007. etc.Handout – Software Testing A detailed description is given below of each of the categories used in the matrix. Eventually record and playback becomes less and less part of the automation process as it is usually more robust to use the built-in functions to directly test objects. a variable. they may use various browsers. exact screen location)? Is there object recognition when recording and playing back or does it appear to record ok but then on playback (without environment change or unique id’s. Informix. As such the test tool should provide good web based test functionality in addition to its client/server functions. Here are a few examples Are there functions to tell me when the page has finished loading? Can I tell the test tool to wait until an image appears? Can I test whether links are valid or not? Can I test web based objects functions like is it enabled. Database Tests Most applications will provide the facility to preserve data outside of itself. etc. Web Testing Web based functionality on most applications is now a part of everyday life. They will record a simple script. All Rights Reserved C3: Protected . checking what is in the backend database usually verifies the proper validation of tests carried out on the front end of an application. look at the code and then playback. is this in an array. In judging the rating for this category I looked at the tools native support for HTML tables. a cursor. Web testing can be riddled with problems if various considerations are not taken into account. Are there facilities that will allow me to programmatically look for objects of a certain type on a web page or locate a specific object? Can I extract data from the web page itself? E. frames. and the screen resolution on their computer will be different. A person may be connecting from the USA or Africa. This is very similar to recording a macro in say Microsoft Access. This is usually achieved by holding the data in a Database. I have looked at all the tools support for SQL. the title? A hidden form element? With Client server testing the target customer is usually well defined you know what network operating system you will be using. Linux or Windows. etc.

extract data? Can you randomise the access to that data? Is the data access truly random? This functionality is normally more important than database tests as the databases will usually have their own interface for running queries. This allows an inexperienced tester/user to run tests by just running/providing the test framework with know commands/variables. databases. databases etc and expose functions. However you may find that most (hopefully) of the application has been implemented using standard objects supported by your test tool vendor but there may be a few objects that are custom ones. address. Frameworks are usually the ultimate goal in deploying automation test tools. etc to create. classes. A test framework has parallels to Software frameworks where you develop an encapsulation layer of software (framework) around the applications. However applications (except for manual input) do not usually provide facilities for bulk data input. All Rights Reserved C3: Protected . we will need to create data to input into the application. Pushbuttons Checkboxes Radio buttons List views Edit boxes Combo boxes If you have a custom object that behaves like one of these are you able to map (tell the test tool that the custom control behaves like the standard) control? Does it support all the standard controls methods? Can you add the custom control to it’s own class of control? Page 120 ©Copyright 2007. Most custom objects will behave like a similar standard control here are a few standard objects that are seen in everyday applications. return data. for the aforementioned bulk data input sometimes carried out in data migration or application upgrades. try to get the development/design team to use standard and not custom objects.Handout – Software Testing Data Functions As mentioned above applications usually provide a facility for storing data off line. etc. etc with variables supplied from an external source usually a CSV (Comma Separated variable) file. etc. Does the tool allow you to specify the type of data you want? Can you automatically generate data? Can you interface with files. to datadriven to framework testing. Then hopefully you will not need this functionality. The added benefit (as I have found) is this functionality can be used for a production reason e. input data. Cognizant Technology Solutions.g. Frameworks provide an interface to all the applications under test by exposing a suitable list of functions. numbers. spreadsheet or database. Data-driven tests are tests that replace hard coded names. methods etc that is used to call the underlying applications. These functions are also very important as you move from the record/playback phase. However to do this requires a lot of time. spreadsheets. skilled resources and money to facilitate the first two. I have looked at all the tools facilities for creating and manipulating data. So to test this. Object Mapping If you are in a role that can help influence the design of a product.

A sort of spy that looks at the internals of the object givi ng you details like the object ame. ID and similar. Does the tool provide OCR (optical character recognition)? Can it compare one image against another? How fast does the compare take? If the compare fails how long does that take? Does the tool allow you to mask certain areas of the screen when comparing. Object Name Map As you test your application using the test tool of your choice you will notice that it records actions against the objects that it interacts with. The last and least desirable should be by coordinates on the screen. All tools provide a search and replace facility but the best implementations are those that provide a central repository to store these object identities. index. the types of errors. I have looked at these facilities in the base tool set. etc. how it recovers from errors. can be programmed to reference windows and object names in one place (say via a variable) and that variable can be used throughout the script (where that object appears). Does the Object Name Map allow you to alias the name or change the name given by the tool to some more meaningful name? Object Identity Tool Once you become more proficient with automation testing one of the primary means of identifying objects will be via an ID Tool. Error recovery caused by the application and environment. Cognizant Technology Solutions. At least one of the tools allows you to map painted controls to standard controls but to do this you have to rely on the screen co-ordinates of the image. These objects are either identified through the coordinates on the screen or preferably via some unique object reference referred to as a tag. Also when the application has painted controls like those in the calculator app found on a lot of windows applications you may need to use this. Page 121 ©Copyright 2007. The premise is it is better to change the reference in one place rather than having to go through each of the scripts to replace it there. object ID. How easy is it to build this into your code? The rating given will depend on how much errors the tool can capture. I looked at built in wizards of the test tools for standard test recovery (when you finish tests or when a script fails). etc. name. All Rights Reserved C3: Protected . it provides the foundation to produce a truly robust test suite. Once you are well into automation and build up 10’s and 100’s of scripts that reference these objects you will want to have a mechanism that provides an easy update if the application being tested changes. Firstly the tool should provide services to uniquely identify each object it interacts with and by various means.Handout – Software Testing Image Testing Lets hope this is not a major part of your testing effort but occasionally you may have to use this to test bit map and similar images. Test/Error recovery This can be one of the most difficult areas to automate but if it is automated. Suppose the application crashes while I am testing what can I do? If a function does not receive the correct information how can I handle this? If I get an error message how do I deal with that? If I access a web site and get a warning what do I do? I cannot get a database connection how do I skip those tests? The test tool should provide facilities to handle the above questions. I found this to be true but not as big a point as some have stated because those tools that don’t support the central repository scheme.

Handout – Software Testing
This will allow you to reference that object within a function call. The tool should give you details of some of the object’s properties, especially those associated with uniquely identifying the object or window. The tool will usually provide the tester with a point and ID service where you can use the mouse to point at the object and in some window you will see all of that objects ID’s and properties. A lot of the tools will allow you to search all the open applications in one swoop and show you the result in a tree that you can look at when required. Extensible Language Here is a question that you will here time and time again in automation forums. “How do I get {insert test tool name here} to do such and such”, there will be one of four answers. I don’t know It can’t do it It can do it using the function x, y or Z It can’t in the standard language but you can do it like this What we are concerned with in this section is the last answer e.g. if the standard test language does not support it can I create a DLL or extend the language in some way to do it? This is usually an advanced topic and is not encountered until the trained tester has been using the tool for at least 6 – 12 months. However when this is encountered the tool should support language extension. If via DLL’s then the tester must have knowledge of a traditional development language e.g. C, C++ or VB. For instance if I wanted to extend a tool that could use DLL’s created by VB I would need to have Visual Basic then open say an ActiveX dll project, create a class containing various methods (similar to functions) then I would make a dll file. Register it on the machine then reference that dll from the test tool calling the methods according to their specification. This will sound a lot clearer as you go on in the tools and this document will be updated to include advanced topics like this in extending the tools capabilities. Some tools provide extension by allowing you to create user defined functions, methods, classes, etc but these are normally a mixture of the already supported data types, functions, etc rather than extending the tool beyond it’s released functionality. Because this is an advanced topic I have not taken into account ease of use, as those people who have got to this level should have already exhausted the current capabilities of the tools. So want to use external functions like win32api functions and so on and should have a good grasp of programming. Environment Support How many environments does the tool support out the box? Does it support the latest Java release, what Oracle, Powerbuilder, WAP, etc. Most tools can interface to unsupported environments if the developers in that environment provide classes, dll’s etc that expose some of the applications details but whether a developer will or has time to do this is another question. Ultimately this is the most important part of automation. Environment support. If the tool does not support your environment/application then you are in trouble and in most cases you will need to revert to manually testing the application (more shelf ware).

Page 122 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
Integration How well does the tool integrate with other tools. This is becoming more and more important. Does the tool allow you to run it from various test management suites? Can you raise a bug directly from the tool and feed the information gathered from your test logs into it? Does it integrate with products like word, excel or requirements management tools? When managing large test projects with an automation team greater than five and testers totaling more than ten. The management aspect and the tools integration moves further up the importance ladder. An example could be a major Bank wants to redesign its workflow management system to allow faster processing of customer queries. The anticipated requirements for the new workflow software numbers in the thousands. To test these requirements 40,000 test cases have been identified 20,000 of these can be automated. How do I manage this? This is where a test management tool comes in real handy. Also how do I manage the bugs raised as a result of automation testing, etc? Integration becomes very important rather than having separate systems that don’t share data that may require duplication of information. The companies that will score larger on these are those that provide tools outside the testing arena as they can build in integration to their other products and so when it comes down to the wire on some projects, we have gone with the tool that integrated with the products we already had. Cost In my opinion cost is the least significant in this matrix, why? Because all the tools are similar in price except Visual Test that is at least 5 times cheaper than the rest but as you will see from the matrix there is a reason. Although very functional it does not provide the range of facilities that the other tools do. Price typically ranges from $2,900 - $5,000 (depending on quantity brought, packages, etc) in the US and around £2,900 - £5,000 in the UK for the base tools included in this document. So you know the tools will all cost a similar price it is usually a case of which one will do the job for me rather than which is the cheapest. Visual Test I believe will prove to be a bigger hit as it expands its functional range it was not that long ago where it did not support web based testing. The prices are kept this high because they can. All the tools are roughly the same price and the volumes of sales is low relative to say a fully blown programming language IDE like JBuilder or Visual C++ which are a lot more function rich and flexible than any of the test tools. On top of the above prices you usually pay an additional maintenance fee of between 10 and 20%. There are not many applications I know that cost this much per license not even some very advanced operating systems. However it is all a matter of supply. The bigger the supply the less the price as you can spread the development costs more. However I do not anticipate a move on the prices upwards as this seems to be the price the market will tolerate. Visual Test also provides a free runtime license.

Page 123 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
Ease Of Use This section is very subjective but I have used testers (my guinea pigs) of various levels and got them from scratch to use each of the tools. In more cases than not they have agreed on which was the easiest to use (initially). Obviously this can change as the tester becomes more experienced and the issues of say extensibility, script maintenance, integration, data-driven tests, etc are required. However this score is based on the productivity that can be gained in say the first three months when those issues are not such a big concern. Ease of use includes out the box functions, debugging facilities, layout on screen, help files and user manuals. Support In the UK this can be a problem as most of the test tool vendors are based in the USA with satellite branches in the UK. Just from my own experience and the testers I know in the UK. We have found Mercury to be the best for support, then Compuware, Rational and last Segue. However having said that you can find a lot of resources for Segue on the Internet including a forum at www.betasoft.com that can provide most of the answers rather than ringing the support line. On their website Segue and Mercury provide many useful user and vendor contributed material. I have also included various other criteria like the availability of skilled resources, online resources, validity of responses from the helpdesk, speed of responses and similar Object Tests Now presuming the tool of choice does work with the application you wish to test what services does it provide for testing object properties? Can it validate several properties at once? Can it validate several objects at once? Can you set object properties to capture the application state? This should form the bulk of your verification as far as the automation process is concerned so I have looked at the tools facilities on client/server as well as web based applications. Matrix What will follow after the matrix is a tool-by-tool comparison under the appropriate heading (as listed above) so that the user can get a feel for the tools functionality side by side. Each category in the matrix is given a rating of 1 – 5. 1 = Excellent support for this functionality, 2 = Good support but lacking or another tool provides more effective support, 3 = Basic/ support only. 4 = This is only supported by use of an API call or third party add-in but not included in the general test tool/below average, 5 = No

Page 124 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing Matrix score Win Runner = 24 QARun = 25 SilkTest = 24 Visual Test = 39 Robot = 24 SUMMARY Automated testing is automating the manual testing process currently in use. All Rights Reserved C3: Protected . Owing to the size and complexity of today’s advanced software applications. manual testing is no longer a viable option for most testing situations. Cognizant Technology Solutions. Page 125 ©Copyright 2007.

Use Robot to record client/server conversations and store them in scripts. A baseline version of RequisitePro is included with Rational Test Manager. RequisitePro organizes your requirements by linking Microsoft Word to a requirements repository and providing traceability and change management throughout the project lifecycle. including enhancement requests. Allows you to write. Rational Suite of tools Rational RequisitePro is a requirements management tool that helps project teams control the development process. A client/server system includes client applications accessing a database or application server. Their Unified Process is a very good development model that allows mapping of requirements to use cases. RequistePro. Rational Suite Performance Studio is a sophisticated tool for automating performance tests on client/server systems. With Clear Quest. Rational Clear Quest is a change-request management tool that tracks and manages defects and change requests throughout the development process. and run tests.Handout – Software Testing Chapter 9: Sample Test Automation Tool Learning Objective After completing this chapter.g. All Rights Reserved C3: Protected . you can manage every type of change activity associated with software development. organize. Clear case. Performance Studio includes Rational Robot and Rational Load Test. defect reports. you will be able to: Work with Rational Testing tool Sample Test Automation Tool Rational offers the most complete lifecycle toolset (including testing) of these vendors for the windows platform. and documentation modifications. including thirdparty libraries. preventing untested code from reaching the end-user. Cognizant Technology Solutions. enabling developers to quickly find. Facilitates functional and performance testing by automating record and playback of test scripts. you can access it in Test Manager. Some of their products are worldwide leaders e. and to capture and analyze the results. Rational Purify is a comprehensive C/C+ + run-time error checking tool that automatically pinpoints run-time errors and memory leaks in all components of an application. prioritize and eliminate performance bottlenecks within an application. ensuring that code is reliable Rational Quantify is an advanced performance profiler that provides application performance analysis. Page 126 ©Copyright 2007. When it comes to Object Oriented development they are the acknowledged leaders with most of the leading OO experts working for them. When you define a test requirement in RequisitePro. test cases and a whole set of tools to support the process. and browsers accessing a Web server. Rational Robot. etc. Rational Pure Coverage is a customizable code coverage analysis tool that provides detailed application analysis and ensures that all code has been exercised. Use Load Test to schedule and play back the scripts. Rational Robot. Rational Rose.

Rational administrator is used to create and manage rational repositories. users and groups and manage security privileges. Cognizant Technology Solutions. A Rational project is associated with one Rational Test data store. and optionally places them under configuration management. All Rights Reserved C3: Protected . How to create a new project? Page 127 ©Copyright 2007. Tests an entire application.Handout – Software Testing Rational Test Factory. one RequisitePro database. one Clear Quest databases. Rational Load Test can emulate hundreds. During playback. even thousands. Rational Test categorizes test information within a repository by project. of users placing heavy loads and stress on your database and Web servers. The tools that are to discussed here are Rational Administrator Rational Robot Rational Test Manager Rational Administrator What is a Rational Project? A Rational project is a logical collection of databases and data stores that associates the data you use when working with Rational Suite. including all GUI features and all lines of source code. Automates testing by combining automatic test generation with ourcecode coverage analysis. and multiple Rose models and RequisitePro projects. You can use the Rational Administrator to create and manage projects.

All Rights Reserved C3: Protected . configure or delete the project. In the above window opened enter the details like Project name and location. enter the Password if you want to protect the project with password. Cognizant Technology Solutions. To manage the requirements assets connect to Requisite Pro. Once the Create button in the Configure project window is chosen. Click Finish. to manage test assets create associated test data store and for defect management connect to Clear quest database. Accept the default path and click OK button. which is required to connect to.Handout – Software Testing Open the Rational administrator and go to File->New Project. Click Next. In the corresponding window displayed. Page 128 ©Copyright 2007. In the configure project window displayed click the Create button. the below seen Create Test Data store window will be displayed.

Handout – Software Testing Once the below window is displayed it is confirmed that the Test datastore is successfully created and click OK to close the window. Cognizant Technology Solutions. All Rights Reserved C3: Protected . Rational Administrator will display your “TestProject” details as below: Page 129 ©Copyright 2007. Click OK in the configure project window and now your first Rational project is ready to play with….

PowerBuilder. Create and edit scripts using the SQABasic. Collect diagnostic information about an application during script playback. The Robot editor provides color-coded commands with keyword Help for powerful integrated programming during script development. Quantify. Robot uses Object-Oriented Recording to identify objects by their internal object names. Robot is integrated with Rational Purify. and VU scripting environments. Test applications developed with IDEs such as Visual Basic. All Rights Reserved C3: Protected . The Object-Oriented Recording technology in Robot lets you generate scripts quickly by simply running and using the application-under-test. Use Robot and TestManager together to record and play back scripts that help you determine whether a multi-client system is performing within user-defined standards under varying loads. VB. Oracle Forms. Record and play back scripts that navigate through your application and test the state of objects through verification points. and Java. HTML. Test objects even if they are not visible in the application's interface. and PureCoverage. Robot can be used to: Perform full functional testing. Page 130 ©Copyright 2007. Robot still finds them on playback. Cognizant Technology Solutions. You can play back scripts under a diagnostic tool and see the results in the log. not by screen coordinates. If objects change locations or their text changes.Handout – Software Testing Rational Robot Rational Robot to develop three kinds of scripts: GUI scripts for functional testing and VU and VB scripts for performance testing. Perform full performance testing.

You can test standard Windows objects and IDEspecific objects. whether they are visible in the interface or hidden. Cognizant Technology Solutions.The type of the script is GUI for functional testing and VU for performance testing. Once logged you will see the robot window.Handout – Software Testing The Object Testing technology in Robot lets you test any object in the application-under-test. including the object's properties and data. All Rights Reserved C3: Protected . Go to File-> New->Script In the above screen displayed enter the name of the script say “First Script” by which the script is referred to from now on and any description (Not mandatory). Page 131 ©Copyright 2007.

The Output window bottom pane) has two tabs: Build – Displays compilation results for all scripts compiled in the last operation. or debugging. To display the Output window: Click View ® Output.Handout – Software Testing The GUI Script top pane) window displays GUI scripts that you are currently recording. How to record a play back script? To record a script just go to Record->Insert at cursor Then perform the navigation in the application to be tested and once recording is done stop the recording. Cognizant Technology Solutions. Line numbers are enclosed in parentheses to indicate lines in the script with warnings and errors. All Rights Reserved C3: Protected . editing. Script pane (right) – Displays the script. Also displays certain system messages from Robot. It has two panes: Asset pane (left) – Lists the names of all verification points and low-level scripts for this script. Record-> Stop Page 132 ©Copyright 2007. Console – Displays messages that you send with the SQAConsoleWrite command.

Handout – Software Testing

In this window we can set general options like identification of lists, menus, recording think time in General tab: Web browser tab: Mention the browser type IE or Netscape… Robot Window: During recording how the robot should be displayed and hotkeys details… Object Recognition Order: the order in which the recording is to happen. For ex: Select a preference in the Object order preference list. If you will be testing C++ applications, change the object order preference to C++ Recognition Order.

Page 133 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing

Go to Tools-> Playback options to set the options needed while running the script. This will help you to handle unexpected window during playback, error recovery, mention the time out period, to manage log and log data. Verification points A verification point is a point in a script that you create to confirm the state of an object across builds of the application-under-test. During recording, the verification point captures object information (based on the type of verification point) and stores it in a baseline data file. The information in this file becomes the baseline of the expected state of the object during subsequent builds When you play back the script against a new build, Robot retrieves the information in the baseline file for each verification point and compares it to the state of the object in the new build. If the captured object does not match the baseline, Robot creates an actual data file. The information in this file shows the actual state of the object in the build. After playback, the results of each verification point appear in the log in Test Manager. If a verification point fails (the baseline and actual data do not match), you can select the verification point in the log and click View ® Verification Point to open the appropriate Comparator. The Comparator displays the baseline and actual files so that you can compare them. Verification point
Page 134 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

Handout – Software Testing
is stored in the project and is always associated with a script. When you create a verification point, its name appears in the Asset (left) pane of the Script window. The verification point script command, which always begins with Result =, appears in the Script (right) pane. Because verification points are assets of a script, if you delete a script, Robot also deletes all of its associated verification points. You can easily copy verification points to other scripts if you want to reuse them. List of Verification Points The following table summarizes each Robot verification point.

Page 135 ©Copyright 2007, Cognizant Technology Solutions, All Rights Reserved C3: Protected

All Rights Reserved C3: Protected .Handout – Software Testing Page 136 ©Copyright 2007. Cognizant Technology Solutions.

sbh: Click File ® Open ® SQABasic File. If recording. Click the Preferences tab. position the pointer in the script and click the Display GUI Insert Toolbar button on the Standard toolbar.SQABasic files are stored in the SQABas32 folder of the project. Click the Comment button on the GUI Insert toolbar. Type the comment (60 characters maximum). Robot provides a blank header file called Global. If editing. To insert a comment into a script during recording or editing. and then click Open. Comments are helpful for documenting and editing scripts. Datapools let you automatically pump test data to virtual testers under high-volume conditions that potentially involve hundreds of virtual testers performing thousands of transactions.sbh. you can insert lines of comment text into a GUI script. Robot ignores comments at compile time. All Rights Reserved C3: Protected . If the file is not there. You can add declarations to this global header file and/or create your own. Robot will check this location first. Adding Declarations to the Global Header File For your convenience.sbh. it will look in the SQABas32 directory. click the Display GUI Insert Toolbar button on the GUI Record toolbar. Global. You can use Robot to create and edit SQABasic header files.sbh. and variables that you want to use with multiple scripts or SQABasic library source files. Select global. SQABasic header files have the extension .sbh). Click OK to continue recording or editing.sbh is a project-wide header file stored in SQABas32 in the project. use the Browse button to find the location. unless you specify another location. Click Edit ® Comment Line or Edit ® Uncomment Line. They can be accessed by all modules within the project. About Data pools A datapool is a test dataset. Robot inserts the comment into the script (in green by default) preceded by a single quotation mark. To open Global. Cognizant Technology Solutions. Set the file type to Header Files (*. For example: This is a comment in the script To change lines of text into comments or to uncomment text: Highlight the text. It supplies data values to the variables in a script during script playback. Inserting a Comment into a GUI Script: During recording or editing. Page 137 ©Copyright 2007. constants.Handout – Software Testing About SQABasic Header Files SQABasic header files let you declare custom procedures. You can specify another location by clicking Tools ® General Options. Under SQABasic path.

A GUI script can access a datapool when it is played back in Robot. Also. Robot compiles the script if it has been modified since it last ran. There is no DATAPOOL_CONFIG statement in a GUI script. you define a datapool for either type of script using TestManager in exactly the same way. You can also compile scripts and SQABasic library source files manually. you might want a datapool to supply those values during playback. Cognizant Technology Solutions. Debug menu The Debug menu has the following commands: Go Go Until Cursor Animate Pause Stop Set or Clear Breakpoints Clear All Breakpoints Step Over Step Into Step Out Note: The Debug menu commands are for use with GUI scripts only. All Rights Reserved C3: Protected . There are differences in the way GUI scripts and sessions are set up for datapool access: You must add datapool commands to GUI scripts manually while editing the script in Robot. Robot adds datapool commands to VU scripts automatically. or when you debug a GUI script. the GUI script can access the same datapool as other scripts. you might want to provide a different set of values each time. when a GUI script is played back in a TestManager suite. Compiling the script When you play back a GUI script or VU script. Using Datapools with GUI Scripts If you are providing one or more values to the client application during GUI recording. and so forth. For example.Handout – Software Testing Typically. The SQADatapoolOpen command defines the access method to use for the datapool. Although there are differences in setting up datapool access in GUI scripts and sessions. you might be filling out a data entry form and providing values such as order number. If you plan to repeat the transaction multiple times during playback. Page 138 ©Copyright 2007. A single virtual tester that performs the same transaction multiple times can send realistic data to the server in each transaction. part name. you use a datapool so that: Each virtual tester that runs the script can send realistic data (which can include unique data) to the server.

The compilation results can be viewed in the Build tab of the Output window. All Rights Reserved C3: Protected . the Build tab in the Output window displays compilation results and error messages with line numbers for all compiled scripts and library source files.Handout – Software Testing During compilation. Cognizant Technology Solutions. Page 139 ©Copyright 2007.

and run reports. Under this single framework. manage. it provides the entire team with one place to go to determine the state of the system at any time. execute tests and evaluate results. Cognizant Technology Solutions. assets. and data both related to and produced by the testing effort. all participants in the testing effort can define and refine the quality goals they are working toward. And. most importantly. log folders. With Test manager we can: Create. All Rights Reserved C3: Protected . The reporting tools help you track assets such as scripts. Rational Test Manager Test Manager is the open and extensible framework that unites all of the tools. Create and manage builds. builds. implement. Create and manage data pools and data types Page 140 ©Copyright 2007.Handout – Software Testing Compilation errors After the script is created and compiled and errors fixed it can be executed. and test documents. In Test Manager you can plan. and logs. The results need to be analyzed in the Test Manager. It is where the team defines the plan it will implement to meet those goals. design. and track test coverage and progress.

Cognizant Technology Solutions. From Test Manager you can know start time of the script and Page 141 ©Copyright 2007. The folder in which the log is to stored and the log name needs to be given in this window. All Rights Reserved C3: Protected . In the Results tab of the Test Manager. you could see the results stored.Handout – Software Testing When the script execution is started the following window will be displayed.

All Rights Reserved C3: Protected . Cognizant Technology Solutions.0 or later Netscape navigator (limited support) Page 142 ©Copyright 2007.0 with service pack 5 Win2000 WinXP(Rational 2002) Win98 Win95 with service pack1 Protocols Oracle SQL server HTTP Sybase Tuxedo SAP People soft Web browsers IE4.Handout – Software Testing Supported environments Operating system WinNT4.

0 or above Visual C++ Java Oracle forms 4.com SUMMARY Rational offers the most complete lifecycle toolset (including testing) of these vendors for the windows platform. VC++ and basic web pages.0 or later. To test these types of application. Rational Rose.0 and above The basic product supports Visual basic. When it comes to Object Oriented development they are the acknowledged leaders with most of the leading OO experts working for them. Some of their products are worldwide leaders e. For more details visit www. Development environments Visual basic 4.g. etc.Handout – Software Testing Markup languages HTML and DHTML pages on IE4.5 Delphi Power builder 5. Cognizant Technology Solutions. Clear case.rational. RequistePro. Rational Robot. All Rights Reserved C3: Protected . Page 143 ©Copyright 2007. you have to download and run a free enabler program from Rational’s website.

however. When looking for errors in the application. A systematic approach like performance analysis is essential to extract maximum benefit from an existing system. you will be able to: Test performance of a software What is Performance testing? The performance testing is a measure of the performance characteristics of an application. One of the main objectives of performance testing is to maintain a web site with low latency. Why Performance testing? Performance problems are usually the result of contention for.e. performance is a secondary issue to features. Page 144 ©Copyright 2007. or exhaustion of. analysis must be done to forecast performance under load. are automated test scripts and an infrastructure to be used to execute automated tests for extended periods. developers would execute their applications using different execution streams (i. Performance testing of an application is basically the process of understanding how the web application and its operating environment respond at various user load levels. This helps to replace and focus efforts at improving overall system response. In such cases. we want to measure the latency. the evaluation of a design alternative is the prime mover for an analysis. high throughput.Handout – Software Testing Chapter 10: Performance Testing Learning Objective After completing this chapter. and low utilization. Cognizant Technology Solutions. the system is unable to scale to higher levels of performance. it is still an issue.. Maintaining optimum Web application performance is a top priority for application developers and administrators. As the user base grows. Post-deployment realities create a need for the tuning the existing system. The main objective of a performance testing is to demonstrate that the system functions to specification with acceptable response times while processing the required transaction volumes in real-time production database. Identification of bottlenecks in a system is more of an effort at troubleshooting. prior to execution. The objective of a performance test is to demonstrate that the system meets requirements for transaction throughput and response times simultaneously. more than one alternative presents itself. Typically to debug applications. When a system resource is exhausted. throughput. In general. To increase confidence and to provide an advance warning of potential problems in case of load conditions. completely exercise the application) in an attempt to find errors. The main deliverables from such a test. some system resource. Performance analysis is also carried for various purposes such as: During a design or redesign of a module or a part of the system. All Rights Reserved C3: Protected . and utilization of the web site while simulating attempts by virtual users to simultaneously access the site. the cost of failure becomes increasingly unbearable.

the design specification or a separate performance requirements document should: Defines specific performance goals for each feature that is instrumented. This helps in determining whether or not the system meets the stated requirements. measurable.expressed in quantifiable terms such that when response times are measured. Relevant . so it pays to make as much use of this infrastructure as possible. The performance testing goals are: End-to-end transaction response time measurements. achievable requirements As a foundation to all tests. Quantitative. which can be re-used for other tests with broader objectives. relevant. Bases performance goals on customer requirements. a sensible comparison can be derived. Measure Application Server components performance under various loads.Handout – Software Testing Performance Testing Objectives The objective of a performance test is to demonstrate that the system meets requirements for transaction throughput and response times simultaneously. Measure database components performance under various loads. Fortunately. Measure the network delay between the server and clients Pre-requisites for Performance Testing We can identify five pre-requisites for a performance test. but rather. Realistic . All Rights Reserved C3: Protected . Cognizant Technology Solutions. performance requirements should be agreed prior to the test. Achievable .response times should take some account of the cost of achieving them. realistic. Measurable . A comprehensive test strategy would define a test infrastructure to enable all these objectives be met. This infrastructure is an asset and an expensive one too. Defines specific customer scenarios. First and foremost thing is. Monitor system resources under various loads. Page 145 ©Copyright 2007.response time requirements should be justifiable when compared with the durations of the activities within the business process the system supports. Quantitative .a response time should be defined such that it can be measured using a tool or stopwatch and at reasonable cost. this infrastructure is a test bed. the list defines what is required before a test can be executed.a response time must be relevant to a business process. The following attributes will help to have a meaningful performance comparison. Not all of these need be in place prior to planning or preparing the test (although this might be helpful).

Database volumes Data volumes. Cognizant Technology Solutions. A load profile is the level of system loading expected to occur during a specific business scenario. middleware or operating systems crash. Testers will not be able to record scripts in the first instance. All Rights Reserved C3: Protected . with some confidence. Load profiles The second component of performance requirements is a schedule of load profiles. the behavior of the target environment. Often this is not possible. Business scenarios might cover different situations when the users’ organization has different levels of activity or involve a varying mix of activities. Even with an environment which is somewhat different from the production environment. users normally focus attention on response times. or may not be able to execute a test for a reasonable length of time before the software. Page 146 ©Copyright 2007. Some functions are critical and require short response times. the test environment should be comparable to the actual production environment. defining the numbers of table rows which should be present in the database after a specified period of live running complete the load profile. Realistic test environment The test environment should ideally be the production environment or a close simulation and be dedicated to the performance test team for the duration of the test. depending on the business application. it should still be possible to interpret the results obtained using a model of the system to predict. If the software crashes regularly. for the results of the test to be realistic. however. A test environment which bears no similarity to the actual production environment may be useful for finding obscure errors in the code. but others are less critical and response time requirements can be less stringent. which must be supported by the system. Performance Testing Requirements Performance requirements normally comprise three components: Response time requirements Transaction volumes detailed in ‘Load Profiles’ Database volumes Response time requirements When asked to specify performance requirements. but is.Handout – Software Testing Stable system A test team attempting to construct a performance test of a system whose software is of poor quality is unlikely to be successful. A single response time requirement for all transactions might be simple to define from the user’s point of view. it will probably not withstand the relatively minor stress of repeated use. data volumes estimated to exist after one year’s use of the systems are used. but is unreasonable. However. and often wishes to define requirements in terms of generic response times. useless for a performance test. but two year volumes or greater might be used in some circumstances. Typically.

All Rights Reserved C3: Protected .Handout – Software Testing Performance Testing Process Page 147 ©Copyright 2007. Cognizant Technology Solutions.

The objective is to understand the performance test requirements. Following are the important performance test requirement that needs to be captured during this phase. Cognizant Technology Solutions. Response Time Transactions Per Second Hits Per Second Workload No of con current users Volume of data Data growth rate Resource usage Hardware and Software configurations Phase 2 – Test Plan The following configuration information will be identified as part of performance testing environment requirement identification. It is important to understand as accurately and as objectively as possible the nature of load that must be generated.Handout – Software Testing Phase 1 – Requirements Study This activity is carried out during the business and technical requirements identification phase. Hardware Platform Server Machines Processors Memory Disk Storage Load Machines configuration Network configuration Page 148 ©Copyright 2007. All Rights Reserved C3: Protected . Hardware & Software components and Usage Model.

Synchronizations points) Data Generation Parameterization/ Data pooling Page 149 ©Copyright 2007. During the test design period the following activities will be carried out: Scenario design Detailed test execution plan Dedicated test environment setup Script Recording/ Programming Script Customization (Delay.Handout – Software Testing Software Configuration Operating System Server Software Client Machine Software Applications Phase 3 – Test Design Based on the test strategy detailed test scenarios would be prepared. Checkpoints. Cognizant Technology Solutions. All Rights Reserved C3: Protected .

Handout – Software Testing Phase 4 –Scripting Phase 5 – Test Execution The test execution will follow the various types of test as identified in the test plan. Virtual user loads are simulated based on the usage pattern and load levels applied as stated in the performance test strategy. All Rights Reserved C3: Protected . The following artifacts will be produced during test execution period: Test logs Test Result Page 150 ©Copyright 2007. Cognizant Technology Solutions. All the scenarios identified will be executed.

All Rights Reserved C3: Protected .Handout – Software Testing Phase 6 – Test Analysis Phase 7 – Preparation of Reports The test logs and results generated are analyzed based on Performance under various load. Network delay. Transaction/second. Think time. Resource usage. database throughput. Cognizant Technology Solutions. Network throughput. Transaction Distribution and Data handling. The following performance test reports/ graphs can be generated as part of performance testing:Transaction Response time Transactions per Second Transaction Summary graph Transaction performance Summary graph Transaction Response graph – Under load graph Virtual user Summary graph Page 151 ©Copyright 2007. Manual and automated results analysis methods can be used for performance results analysis.

Workload Not trivial Biased Goals ‘To show that OUR system is better than THEIRS” Analysts = Jury Unsystematic Approach Analysis without Understanding the Problem Incorrect Performance Metrics Unrepresentative Workload Wrong Evaluation Technique Overlook Important Parameters Ignore Significant Factors Inappropriate Experimental Design Inappropriate Level of Detail No Analysis Erroneous Analysis Page 152 ©Copyright 2007. Cognizant Technology Solutions. database organization. Common Mistakes in Performance Testing No Goals No general purpose model Goals =>Techniques. Metrics.Handout – Software Testing Error Statistics graph Hits per second graph Throughput graph Down load per second graph Based on the Performance report analysis. network capacity or routing. middleware. Changes to server system parameters. All Rights Reserved C3: Protected . Upgrades to client or server hardware. suggestions on improvement or tuning will be provided to the design team: Performance improvements to application software.

we should run the performance test suite under controlled conditions from build to build. The performance tests should be modified consistently. Establish incremental performance goals throughout the product development cycle. it is a software architectural problem. at how to instrument tests to best measure various response times. Creating an automated test suite to measure performance is time-consuming and labor-intensive. the management team must decide to enforce the goals. Design the performance test suite to measure response times and not to identify bugs in the product. the tool can also assess Internet Server Application Programming Interface and application server provider (ISAPI/ASP) applications. keep the performance test suite fairly static throughout the product development cycle. Performance issues must be identified as soon as possible to prevent further degradation. without a clear purpose. Design the build verification test (BVT) suite to ensure that no new bugs are injected into the build that would prevent the performance test suite from successfully completing. Without defined performance goals or requirements. The Web Capacity Analysis (WebCAT) tool provides Web server performance analysis. testers must guess. it is important to define concrete performance goals. Significant changes to the performance test suite skew or make obsolete all previous data. Therefore. If the design or requirements change and you must modify a test. We should run the automated performance test suite against every build and compare the results against previous results. Cognizant Technology Solutions. Page 153 ©Copyright 2007. Performance testing of Web services and applications is paramount to ensuring an excellent customer experience on the Internet. Also. Therefore. perturb only one variable at a time for each build. The performance tests should not be used to find functionality-type bugs. All Rights Reserved C3: Protected . Performance goals need to be ensured.Handout – Software Testing No Sensitivity Analysis Ignoring Errors in Input Improper Treatment of Outliers Assuming No Change in the Future Ignoring Variability Too Complex Analysis Improper Presentation of Results Ignoring Social Aspects Omitting Assumptions and Limitations Benchmarking Lessons Ever build needs to be measured. If we decide to make performance a goal and a measure of the quality criteria for release. This typically means measuring performance on "clean" test environments. All the members in the team should agree that a performance issue is not just a bug.

When Webload runs the test.Webload displays them in graphs and tables in real-time and you can save and export the results when the test is finished. Cognizant Technology Solutions. Ensure that you know what you are measuring and why. Webload generates load by creating virtual clients that emulate network traffic. Achieving performance goals early also helps to ensure that the ship date is met because a product rarely ships if it does not meet performance goals. it gathers results at a per-client. Performance Testing Tools Testing for most applications will be automated.5 and Webload 4. Page 154 ©Copyright 2007. WebLoad 4. per-transaction and per-instance level from the computers that are generating the load. including cookies. All Rights Reserved C3: Protected . these Virtual users provide consistent.1. Performance is known to degrade slightly during the stabilization phase of the development cycle. Use WebLoad to test how well your web site will perform under realworld conditions by combining performance. TSL. It can measure the performance of your application under any load conditions.0 and 1. Using a minimum of hardware resources. persistent connections and chunked transfer coding. Repeatable and measurable load to execute your client/server system just as real users would. You create test scripts (called agendas) using Java Scripts that instruct those virtual clients about what to do. Tests are capturing secondary metrics when the instrumented tests have nothing to do with measuring clear and established performance goals. For example. if the data is not going to be used in a meaningful way to make improvements in the engineering cycle.Handout – Software Testing Strive to achieve the majority of the performance goals early in the product development cycle because: Most performance issues require architectural change. authentifications. Webload supports HTTP1. SSL. Although secondary metrics look good on wall charts and in reports. You can watch the results as they occur. it is probably wasted data. Webload can also gather information server’s performance monitor. LoadRunner enables you to test your system under controlled and peak load conditions. functionality and performance of Web-based applications – both Internet and Intranet. You should reuse automated performance tests Automated performance tests can often be reused in many other automated test suites.5x. The tools used for performance testing are Loadrunner 6. incorporate the performance test suite into the stress test suite to validate stress scenarios and to identify potential performance issues under different stress conditions. LoadRunner runs thousands of Virtual Users that are distributed over a network. load and functional tests or by running them individually. Load Runner’s in depth reports and graphs provide the information that you need to evaluate the performance of your client/server system. proxies. client certificates.5 Webload is a testing tool for testing the scalability.5 LoadRunner is Mercury Interactive’s tool for testing the performance of client/server systems. LoadRunner 6. To generate load. Tools used for testing would be the tool pecified in the requirement specification.

All Rights Reserved C3: Protected .Handout – Software Testing Performance Testing Tools . Cognizant Technology Solutions.summary and comparison Page 155 ©Copyright 2007.

All Rights Reserved C3: Protected . Cognizant Technology Solutions.Handout – Software Testing Page 156 ©Copyright 2007.

Cognizant Technology Solutions.Handout – Software Testing Page 157 ©Copyright 2007. All Rights Reserved C3: Protected .

Handout – Software Testing Page 158 ©Copyright 2007. Cognizant Technology Solutions. All Rights Reserved C3: Protected .

Cognizant Technology Solutions. All Rights Reserved C3: Protected .Handout – Software Testing Architecture Benchmarking Hardware Benchmarking . This is achieved through software benchmark test.Hardware benchmarking is performed to size the application with the planned Hardware platform. It is significantly different from capacity planning exercise in that it is done after development and before deployment Software Benchmarking . Page 159 ©Copyright 2007.Defining the right placement and composition of software instances can help in vertical scalability of the system without addition of hardware resources.

Methodology: a list of suggested steps to take in order to assess the system under test. Or. This methodology specification provides information on the appropriate script of pages or transactions for the user. Utilization: The fraction of time the resource is busy servicing requests. Methodology Definitions Result: provide information about what the test will accomplish. each test requires a certain type of workload. Page 160 ©Copyright 2007. E. Stretch Factor: The ratio of the response time with single user to that of concurrent users.Handout – Software Testing General Tests What follows is a list of tests adaptable to assess the performance of most systems. Time estimate: a rough estimate of the amount of time that the test may take to complete. The response time at maximum throughput is too high. the ratio of the performance of an nprocessor system to that of a one-processor system is its efficiency. Purpose: explains the value and focus of the test. All Rights Reserved C3: Protected . What to look for: contains information on behaviors. Type of workload: in order to properly achieve the goals of the test. along with some simple background information that might be helpful during testing. bandwidth in bits per second.. Constraints: details any constraints and values that should not be exceeded during testing. Throughput: Rate (requests per unit of time) Examples: Jobs per second Requests per second Millions of Instructions Per Second (MIPS) Millions of Floating Point Operations Per Second (MFLOPS) Packets Per Second (PPS) Bits per second (bps) Transactions Per Second (TPS) Capacity: Nominal Capacity: Maximum achievable throughput under ideal workload conditions. Usable capacity: Maximum throughput achievable without exceeding a pre-specified response-time limit Efficiency: Ratio usable capacity to nominal capacity. allowing one to use a wide range of tools to conduct the assessments. issues and errors to pay attention to during and after the test.g. Performance Metrics The Common Metrics selected /used during the performance testing is as below Response time Turnaround time = the time between the submission of a batch job and the completion of its output. The methodologies below are generic. Cognizant Technology Solutions.

JDBC Connection Pool Database Server Resources–Wait Events.e strategy. disk space and network usage on individual web.Handout – Software Testing Average Fraction used for memory. All Rights Reserved C3: Protected . Memory and Disk Space Web Server Resources–Threads. execution.. Cognizant Technology Solutions. Without the rigor described in this paper. analysis and reporting. metrics such as response times for transactions. design. should be collected. memory. throughput etc. application and database servers and make sure those numbers recede as load decreases. It is also important to monitor and collect the statistics such as CPU utilization. plan. executing performance testing does not yield anything more than finding more defects in the system. HTTP requests per second. As tests are executed. Third party monitoring tools are also used based on the requirement. if executed systematically with appropriate planning. SQL Queries Transaction Profiling Code Block Analysis Network Statistics Bandwidth Utilization Network delay time Network Segment delay time Conclusion Performance testing is an independent discipline and involves all the phases as the mainstream testing lifecycle i. However. performance testing can unearth issues that otherwise cannot be done through mainstream testing.Processor Utilization. Client Side Statistics Running Vusers Hits per Second Throughput HTTP Status Code HTTP responses per Second Pages downloaded per Second Transaction response time Page Component breakdown time Page Download time Component size Analysis Error Statistics Errors per Second Total Successful/Failed Transactions Server Side Statistics System Resources . Cache Hit Ratio Application Server Resources–Heap size. It is very typical of the project manager to be overtaken by time and resource pressures Page 161 ©Copyright 2007. Cognizant has built custom monitoring tools to collect the statistics.

Cognizant Technology Solutions. Testing of critical web applications during its development and before its deployment should include functional testing to confirm to the specifications. If not. lifecycle-focused approach. All Rights Reserved C3: Protected . enabling new business opportunity lowering transaction costs and strengthening profitability. the consequences of which could be disastrous to the final system. Fortunately. Before testing the system for performance requirements. However there is an important point to be noted here. The discipline helps businesses succeed in leveraging Web technologies to their best advantage. Once these solutions are properly adopted and utilized. Web-enabled applications and infrastructures must be able to execute evolving business processes with speed and precision while sustaining high volumes of changing and unpredictable user audiences. Load Testing Load Testing is creation of a simulated load on a real computer system by using virtual users who submit work as real users would do at real client workstations and thus testing the systems ability to support such workload. the system should have been architect and designed for meeting the required performance goals. robust and viable solutions exist to help fend off disasters that result from poor performance. Automated load testing tools and services are available to meet the critical need of measuring and optimizing complex and dynamic application and infrastructure performance. Thus a load testing is accomplished by stressing the real application under simulated load provided by virtual users. There is another flip side of the coin. it may be too late in the software development cycle to correct serious performance issues. Load testing gives the greatest line of defense against poor performance and accommodates complementary strategies for performance management and monitoring of a production environment. business can confidently and proactively execute strategic corporate initiatives for the benefit of shareholders and customers alike. businesses can begin to take charge and leverage information technology assets to their competitive advantage. leveraging an ongoing. Page 162 ©Copyright 2007. performance testing to check if it offers an acceptable response time and load testing to see what hardware or software configuration will be required to provide acceptable response time and handle the load that will created by the real users of the system Why is load testing important? Load Testing increases the uptime for critical web applications by helping you spot the bottlenecks in the system under large user stress scenarios before they happen in a production environment. By continuously testing and monitoring the performance of critical software applications. When should load testing be done? Load testing should be done when the probable cost of the load test is likely less than the cost of a failed application deployment.Handout – Software Testing leading not enough budget being allocated for performance testing.

and data components. hardware. queries that return the entire contents of a database. Objectives The typical objectives of stress testing are to: Partially validate the application (i. Batch with no realtime requirements. Cognizant Technology Solutions. Help determine the extent to which the application is ready for launch. Volume testing will seek to verify the physical and logical limits to a system's capacity and ascertain whether such limits are acceptable to meet the projected capacity of the organization's business processing. as conditions become extreme..g. stress testing could involve an extreme number of simultaneous users. Goals The typical goals of stress testing are to: Cause the application to fail to scale gracefully under extreme conditions so that the underlying defects can be identified. number of users... Such systems can be transactions processing systems capturing real time sales or could be database updates and or data retrieval. and prevented in the future. insufficient memory inadequate hardware. or an entry at the maximum amount of data in a field. as its name implies. A system including software.e.g.Handout – Software Testing Volume and Stress Testing Volume testing: Volume Testing. Stress testing is the system testing of an integrated. Page 163 ©Copyright 2007. is testing that purposely subjects a system (both hardware and software) to a series of tests where the volume of data being processed is the subject of the test. extreme utilization. fixed. blackbox application that attempts to cause failures involving how its performance varies under extreme but valid conditions (e. amount of data). and dependency on over-utilized shared resources). All Rights Reserved C3: Protected . Provide input to the defect trend analysis effort. Configuration and/or Stress Testing. analyzed. Determine how an application degrades and eventually fails. Provide data that will assist systems engineers in making intelligent decisions regarding future scaling needs. extreme numbers of transactions. Report these failures to the development teams so that the associated defects can be fixed. Determine if the application will support "worst case" production load conditions. Volume Testing is conducted in conjunction with Component. queries with an extreme number of restrictions. to determine if it fulfills its scalability requirements). Examples Typical examples include stress testing of an application that is: Software only. For example. Huge (e. number of transactions.

The test suites for every scheduled scalability requirement execute successfully. All Rights Reserved C3: Protected . Test Implementation: o Develop test scripts o Simulating extreme workloads.e. Software integration has occurred (i. Embeded within another system (e.Handout – Software Testing Soft realtime (i. Test Execution: o o Regression Testing Profiling Test Reporting Environments Load testing is typically performed on the following environments using the following tools: Test Environment: o Test Harness o Use case modeling tool o Performance analyzer o Profiler Page 164 ©Copyright 2007. The relevant system components have passed system integration testing. A research prototype that will not be placed into service. flight-control software.g. The test environment is ready.. Cognizant Technology Solutions. human reaction times). load testing can begin prior to the distribution of the software components onto the hardware components). The independent test team is adequately staffed and trained in stress testing.. The relevant software components have passed unit testing. Client/server or n-tier distributed. Business-critical or safety-critical. avionics. cruise-control software).e..g. Preconditions Stress test execution can typically begin when the following preconditions hold: The scalability requirements to be tested have been specified. automotive engine control).. Hard realtime (e. Tasks Stress testing typically involves the independent test team performing the following testing tasks using the following techniques: Test Planning Test Reuse Test Design: o o Use Case Based Testing Workload analysis to determine the maximum production workloads. Completion Criteria Stress testing is typically complete when the following postconditions hold: At least one stress test suite exists for each scalability requirement. radar.

Handout – Software Testing Work Products Stress testing typically results in the production of all or part of the following work products from the test work product set: Documents: o Project Test Plan o Master Test List o Test Procedures o Test Report o Test Summary Report Software and Data: o o o o o Phases Test Harness Test Scripts Test Suites Test Cases Test Data (*) Optional stress testing of COTS software components during the technology analysis and technology vendor selection tasks. (**) Optional stress testing of the executable architecture as well as the COTS components during the vendor and tool evaluation and vendor and tool selection tasks. Cognizant Technology Solutions. All Rights Reserved C3: Protected . Page 165 ©Copyright 2007.

Develop test scripts simulating exceptional workloads. Page 166 ©Copyright 2007. Perform stress testing for several minutes to several hours. Stress testing must be automated if adequate regression testing is to occur. prior to execution. To the extent practical. SUMMARY The performance testing is a measure of the performance characteristics of an application. reuse functional test cases as stress test cases. The iterative and incremental development cycle implies that stress testing is regularly performed in an iterative and incremental manner.Handout – Software Testing Guidelines A system can fulfilits operational requirements and still be a failure if it does not scale. The main deliverables from such a test. Stress testing can elicit failures prior to launch. Cognizant Technology Solutions. The main objective of a performance testing is to demonstrate that the system functions to specification with acceptable response times while processing the required transaction volumes in real-time production database. are automated test scripts and an infrastructure to be used to execute automated tests for extended periods. All Rights Reserved C3: Protected . The objective of a performance test is to demonstrate that the system meets requirements for transaction throughput and response times simultaneously.

the application is classified into various modules like say for a web application. you will be able to: Describe TCP and TCP Analysis What is a Test Case Point (TCP)? TCP is a measure of estimating the complexity of an application. Test Case Point Analysis Calculating the Test Case Points Based on the Functional Requirement Document (FRD). All Rights Reserved C3: Protected . The TCP counts are nothing but ranking the requirements and the test cases that are to be written for those requirements into simple. In this courseware we shall give an overview about Test Case Points and not elaborate on using TCP as an estimation technique. The test cases for a particular requirement are classified into Simple. Cognizant Technology Solutions. of verification points OR Baseline Test data Refer the test case classification table given below Page 167 ©Copyright 2007. A Complex requirement is ranked between 8 and 10. An Average requirement is ranked between 4 and 7. which can be given a value in the scale of 1 to3. average and complex and quantifying the same into a measure of complexity. This is also used as an estimation technique to calculate the size and effort of a testing project. Average and Complex based on the number and complexity of the requirements for that module. we can have ‘Login and Authentication’ as a module and rank that particular module as Simple.Handout – Software Testing Chapter 11: Test Case Point Learning Objective After completing this chapter. Test case complexity for that requirement OR Interface with other Test cases OR No. Average and Complex based on the following four factors. A Simple requirement is one.

From the break up of Complexity of Requirements done in the first step. average and complex test cases. Any verification point containing a calculation is considered 'Complex' Any verification point. Summing up the three results.Handout – Software Testing A sample guideline for classification of test cases is given below. we get the simple. average and complex test case types. Cognizant Technology Solutions. Page 168 ©Copyright 2007. By multiplying the number of requirements with it s corresponding adjustment factor. which interfaces with or interacts with another application is classified as 'Complex' Any verification point consisting of report verification is considered as 'Complex' A verification point comprising Search functionality may be classified as 'Complex' or 'Average' depending on the complexity Depending on the respective project. the complexity needs to be identified in a similar manner. we arrive at the count of Total Test Case Points. This adjustment factor has been calculated after a thorough study and analysis done on many testing projects. we can get the number of simple. All Rights Reserved C3: Protected . average and complex test case points. The Adjustment Factor in the table mentioned below is pre-determined and must not be changed for every project. Based on the test case type an adjustment factor is assigned for simple.

Test coverage analysis is sometimes called code coverage analysis. without regard to how it works internally. Test coverage measures A large variety of coverage measures exist.Handout – Software Testing Test Coverage Test Coverage is an important measure of quality for software systems. and not the quality of the actual product. All Rights Reserved C3: Protected . A test coverage analyzer automates this process. If the execution time in some procedures is zero. which is an indirect measure of quality. The two terms are synonymous. Code coverage analysis is a structural testing technique (white box testing). Page 169 ©Copyright 2007. taking into account possible pitfalls in the structure and logic. Creating additional test cases to increase coverage. Test coverage analysis can be used to assure quality of the set of tests. But this measure of test coverage is so coarse-grained it's not very practical. Test Coverage analysis is the process of: Finding areas of a program not exercised by a set of test cases. whose job is really to measure performance bottlenecks. Here is a description of some fundamental measures and their strengths and weaknesses Procedure-Level Test Coverage Probably the most basic form of test coverage is to measure what procedures were and were not executed during the test suite. Also an optional aspect of test coverage analysis is: Identifying redundant test cases that do not increase coverage. you need to write new tests that hit those procedures. Structural testing compares test program behavior against the apparent intention of the source code. and Determining a quantitative measure of code coverage. Structural testing examines how the program works. The academic world more often uses the term "test coverage" while practitioners more often use "code coverage". This contrasts with functional testing (black-box testing). Functional testing examines what the program accomplishes. Coverage analysis requires access to test program source code and often requires recompiling it with a special command. which compares test program behavior against a requirements specification. This simple statistic is typically available from execution profiling tools. Cognizant Technology Solutions.

The same executable file used for product release testing should be used for code coverage. How and when this instrumentation phase happens can vary greatly between different products. Source-Level Instrumentation Some products add probes at the source level. There are many other test coverage measures. it is dependent on operating environment -. etc.the provider of the tool must explicitly choose which languages to support. a statement in an if clause). But it can be somewhat independent of operating environment (processor. you can see exactly what functionality has not been tested. Adding probes to the program will make it bigger and slower. One drawback of this technique is the need to modify the build process. the file itself is not modified. This type of instrumentation is independent of programming language.g. A large project that achieved 90% code coverage might be considered a well-tested product. Executable Instrumentation Probes can also be added to a completed executable file. OS. code coverage version in addition to other versions. Runtime Instrumentation Probes need not be added until the program is actually run. Cognizant Technology Solutions. if you achieve 95+% line coverage and still have time and budget to commit to further testing improvements.) than other forms of instrumentation. You need condition coverage to know. Condition Coverage and Other Measures It's easy to find cases where line coverage doesn't really tell the whole story. Because the file is not modified in any way. This result is often presented in a summary at the procedure. But in practice. This type of instrumentation is dependent on programming language -. it is an enviable commitment to quality! How Test Coverage Tools Work To monitor execution. test coverage tools generally "instrument" the program by inserting "probes". If that code is shown as executed. intercept the compiler after parsing but before code generation to insert the changes they need. In theory. for example. Some products. of course. and add additional code (such as calls to a code coverage runtime) that will record where the program reached. Such a tool may not actually generate new source files with the additional code. is often the key to writing more tests that will increase coverage: By studying the unexecuted code. the performance factor may be significant. and then create a new.. you don't know whether you have tested the case when it is skipped. such as debug (un optimized) and release (optimized) needs to be maintained. file. All Rights Reserved C3: Protected .Handout – Software Testing Line-Level Test Coverage The basic measure of a dedicated test coverage tool is tracking which lines of code are executed. However. A separate version namely. you should have more. The tool will analyze the existing executable. The probes exist only in the inmemory copy of the executable file. most available code coverage tools do not provide much beyond basic line coverage. Proponents claim this technique can provide higher levels of code coverage measurement (condition coverage. If the test suite is large and timeconsuming. or project level giving a percentage of the code that was executed. They analyze the source code as written. However.the provider of the tool must explicitly choose which processors or virtual machines to support. consider a block of code that is skipped under certain conditions (e. just executing it will not automatically start code coverage (as it would with the other methods of Page 170 ©Copyright 2007. allowing you to see exactly which lines of code were executed and which were not. This. For example. instrumented one. and which are not. or virtual machine). Typically the line coverage information is also presented at the source code level.

We must set a higher coverage goal for unit testing than for system testing since a failure in lower-level code may affect multiple high-level callers. Test Coverage Tools at a Glance Coverage analysis is a structural testing technique that helps eliminate gaps in a test suite. and does nothing if the coverage tool is not waiting. Clearly. Instead. up-to-date requirements specification. All Rights Reserved C3: Protected . This new code will wake up and connect to a waiting coverage tool whenever the program executes. It helps most in the absence of a detailed. Each project must choose a minimum percent coverage for release criteria based on available testing resources and the importance of preventing post-release failures.Handout – Software Testing instrumentation). Runtime Instrumentation is independent of programming language but dependent on operating environment. safety-critical software should have a high goal. This added code does not affect the size or performance of the executable. the code coverage tool will add a tiny bit of instrumentation to the executable. the code coverage tool must start program execution directly or indirectly. Cognizant Technology Solutions. Alternatively. Page 171 ©Copyright 2007. Like Executable Instrumentation.

Country. document.name1. The details that can be stored are Name. Case Study: Application Personal Address book. The phone number and credit card number are numeric and email address is also verified for a character '@'.value=="") { alert ("Please Fill in the name"). } if (document.frm. City. The Personal Address book is designed for people to access their contacts online from a central database on the server. State. Validation code at client side function save() { var flag.frm.focus().frm. These entries can be modified directly from here by clicking the edit button. so that effectively reduces the network traffic. Note that the pages are not submitted to the server for this action. Test your Understanding Assignment 1 There is an application on personal address book. However the system is not compatible with Netscape browser and is designed specifically for the IE 5.value=="") Page 172 ©Copyright 2007. It uses ASP in the server side and java script in the client side. The database is Microsoft Access. along with email is displayed. However only the name and phone numbers are mandatory fields. Address2. Cognizant Technology Solutions.name1. All Rights Reserved C3: Protected .Handout – Software Testing SUMMARY TCP is a measure of estimating the complexity of an application. Address1.phone. an additional field for credit card number is provided. if (document. The search page provides with facility to search by name or place and the results are displayed in a tabular form where the essential fields name and phone no. return false. Phone no. The view only pages are reached through the results page on clicking the hyperlinks. find the independent paths b) Develop Test cases based on that.0 and above. This is also used as an estimation technique to calculate the size and effort of a testing project. you need to submit the following artifacts: a) Draw the flow chart. The entries can be seen in a tabular form also by choosing the search by list option. As a whole it is designed for personal use and security was not a concern while designing it. Email address. In the personal information page. c) Also develop other test cases for complete testing.. flag=0.

return false. document.email.focus(). } } if (flag!=1) { alert ("Please Fill email in correct format").value. } if (isNaN(document.charAt(i)=="@") { flag=1. document. } } document. return false. document. return true.email. break.frm.frm.frm.i++) { if (document.frm.frm.i<document. } if (document.email.select().frm.phone. document.frm.phone.frm. document. All Rights Reserved C3: Protected . } Page 173 ©Copyright 2007.focus(). Cognizant Technology Solutions.phone.select().phone.submit().value)==true) { alert ("Phone number should be numeric").value.frm.frm.Handout – Software Testing { alert ("Please Fill in the Phone number").length.email.email.value!="") { for (i=0. return false.focus().

Cognizant Technology Solutions. Mark Fewster & Dorothy Graham Black-Box Testing . Hung Q.tripod. by. Glenford J. Linda G. Rex Black 50 Ways to improve your testing. by.softwaretestinginstitute. and Performance.Michael Hacke & Robert Johnson Software Testing: A Craftsman's Approach. Nguyen.Bob Johnson .com/ Cognizant eResources: http://elibrary/ \\ctsintcosaca\library BOOKS The Art of Software Testing. Hung Q. Hayes Automating Specification-Based Software Testing. Mosley Fundamental Concepts for the Software Quality Engineer. by.com/ http://www. by.co. Boris Beizer Automated Testing Handbook. All Rights Reserved C3: Protected . by. by. by. by. by.uk/ http://www. Paulc. Management. Boris Beizer Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems. by. by. Jeff Rashka.softwaretesting. Robert M. Myers The Complete Guide to Software Testing.edu/~storm/ http://www. Elfriede Dustin. by. by.sqatester. Poston. by. Boris Beizer Client Server Software Testing on the Desktop and the Web. by.com/resources. Bill Hetzel Software Testing Techniques.html http://www.testing. Daniel J. John Paul & Paperback Practical Tools and Techniques for Managing Hardware and Software Testing. IEEE Black Box Testing.com/ http://www. Mark Fewster & Dorothy Graham The craft of software testing.softwareqatest.aptest. by. Brian Marick Software test automation.nildram. Taz Daughtrey Testing Applications on the Web. by. Nguyen Software Test Automation. Bret Pettichord Page 174 ©Copyright 2007. Jorgensen.com/ http://www. Paul Jorgensen Automated Software Testing: Introduction. Elfriede Dustin Effective use of Test automation tools.com/~bazman/ http://www. by. by.Handout – Software Testing REFERENCES WEBSITES http://members.mtsu.

All Rights Reserved C3: Protected . Cognizant Technology Solutions.Handout – Software Testing STUDENT NOTES: Page 175 ©Copyright 2007.

Sign up to vote on this title
UsefulNot useful