Software Testing
Table of Contents
1 INTRODUCTION TO SOFTWARE ... 7
1.1 EVOLUTIONOFTHE SOFTWARE TESTINGDISCIPLINE ... 7
1.2 THE TESTINGPROCESSANDTHE SOFTWARE TESTING LIFE CYCLE ... 7
1.3 BROAD CATEGORIESOF TESTING ... 8
1.4 WIDELYEMPLOYED TYPESOF TESTING ... 8
1.5 THE TESTING TECHNIQUES ... 9
1.6 CHAPTER SUMMARY ... 9
2 BLACK BOX AND WHITE BOX TESTING ... 11
2.1 INTRODUCTION ... 11
2.2 BLACKBOXTESTING ... 11
2.3 TESTING STRATEGIES/TECHNIQUES ... 13
2.4 BLACKBOXTESTING METHODS ... 14
2.5 BLACK BOX (VS) WHITE BOX ... 16
2.6 WHITE BOX TESTING ... 18
3 GUI TESTING ... 23
3.1 SECTION 1 - WINDOWS COMPLIANCE TESTING ... 23
3.2 SECTION 2 - SCREEN VALIDATION CHECKLIST ... 25
3.3 SPECIFIC FIELD TESTS ... 29
3.4 VALIDATION TESTING - STANDARD ACTIONS ... 30
4 REGRESSION TESTING ... 33
4.1 WHATISREGRESSION TESTING ... 33
4.2 TEST EXECUTION ... 34 4.3 CHANGE REQUEST ... 35 4.4 BUG TRACKING ... 35 4.5 TRACEABILITY MATRIX ... 36 5 PHASES OF TESTING ... 39 5.1 INTRODUCTION ... 39
5.2 TYPESAND PHASESOF TESTING ... 39
5.3 THE “V”MODEL ... 40
... 42
6 INTEGRATION TESTING ... 43
6.1 GENERALIZATIONOFMODULETESTINGCRITERIA ... 44
... 46
7 ACCEPTANCE TESTING ... 49
7.1 INTRODUCTION – ACCEPTANCE TESTING ... 49
7.2 FACTORSINFLUENCING ACCEPTANCE TESTING ... 49
7.3 CONCLUSION ... 50
8 SYSTEM TESTING ... 51
8.1 INTRODUCTIONTO SYSTEM TESTING ... 51
8.3 SYSTEM TESTING TECHNIQUES ... 52
8.4 FUNCTIONALTECHNIQUES ... 53
8.5 CONCLUSION: ... 53
9 UNIT TESTING ... 54
9.1 INTRODUCTIONTO UNIT TESTING ... 54
9.2 UNIT TESTING –FLOW: ... 55
1 RESULTS ... 55
UNIT TESTING – BLACK BOX APPROACH ... 56
UNIT TESTING – WHITE BOX APPROACH ... 56
UNIT TESTING – FIELD LEVEL CHECKS ... 56
UNIT TESTING – FIELD LEVEL VALIDATIONS ... 56
UNIT TESTING – USER INTERFACE CHECKS ... 56
9.3 EXECUTIONOF UNIT TESTS ... 57
UNIT TESTING FLOW : ... 57
DISADVANTAGE OF UNIT TESTING ... 59
METHODFOR STATEMENT COVERAGE ... 59
RACE COVERAGE ... 60
9.4 CONCLUSION ... 60
10 TEST STRATEGY ... 62
10.1 INTRODUCTION ... 62
10.2 KEYELEMENTSOF TEST MANAGEMENT: ... 62
10.3 TEST STRATEGY FLOW : ... 63
10.4 GENERAL TESTING STRATEGIES ... 65
10.5 NEEDFOR TEST STRATEGY ... 65
10.6 DEVELOPINGA TEST STRATEGY ... 66
10.7 CONCLUSION: ... 66
11 TEST PLAN ... 68
11.1 WHATISA TEST PLAN? ... 68
CONTENTSOFA TEST PLAN ... 68
11.2 CONTENTS (INDETAIL) ... 68
12 TEST DATA PREPARATION - INTRODUCTION ... 71
12.1 CRITERIAFOR TEST DATA COLLECTION ... 72
15 DEFECT MANAGEMENT ... 95
15.1 DEFECT ... 95
15.2 DEFECT FUNDAMENTALS ... 95
15.3 DEFECT TRACKING ... 96
15.4 DEFECT CLASSIFICATION ... 97
15.5 DEFECT REPORTING GUIDELINES ... 98
16 AUTOMATION ... 101
16.1 WHY AUTOMATETHE TESTING PROCESS? ... 101
16.2 AUTOMATION LIFE CYCLE ... 103
16.3 PREPARINGTHE TEST ENVIRONMENT ... 105
16.4 AUTOMATION METHODS ... 108
17 GENERAL AUTOMATION TOOL COMPARISON ... 111
17.1 FUNCTIONAL TEST TOOL MATRIX ... 111
17.2 RECORDAND PLAYBACK ... 111
17.3 WEB TESTING ... 112
17.4 DATABASE TESTS ... 112
17.5 DATA FUNCTIONS ... 112
17.6 OBJECT MAPPING ... 113
17.7 IMAGE TESTING ... 114
17.8 TEST/ERRORRECOVERY ... 114
17.9 OBJECT NAME MAP ... 114
17.10 OBJECT IDENTITY TOOL ... 115
17.11 EXTENSIBLE LANGUAGE ... 115 17.12 ENVIRONMENT SUPPORT ... 116 17.13 INTEGRATION ... 116 17.14 COST ... 116 17.15 EASE OF USE ... 117 17.16 SUPPORT ... 117 17.17 OBJECT TESTS ... 117 17.18 MATRIX ... 118 17.19 MATRIXSCORE ... 118
18 SAMPLE TEST AUTOMATION TOOL ... 119
18.1 RATIONAL SUITEOFTOOLS ... 119
18.2 RATIONAL ADMINISTRATOR ... 120
18.3 RATIONAL ROBOT ... 124
18.4 ROBOTLOGINWINDOW ... 125
18.5 RATIONAL ROBOTMAINWINDOW-GUI SCRIPT ... 126
18.6 RECORDAND PLAYBACKOPTIONS ... 127
18.7 VERIFICATIONPOINTS ... 129
18.8 ABOUT SQABASIC HEADER FILES ... 131
18.9 ADDING DECLARATIONSTOTHE GLOBAL HEADER FILE ... 131
18.10 INSERTINGA COMMENTINTOA GUI SCRIPT: ... 131
18.11 ABOUT DATAPOOLS ... 132
18.12 DEBUGMENU ... 132
18.13 COMPILINGTHESCRIPT ... 133
19 RATIONAL TEST MANAGER ... 135
19.1 TEST MANAGER-RESULTSSCREEN ... 136
20 SUPPORTED ENVIRONMENTS ... 138 20.1 OPERATINGSYSTEM ... 138 20.2 PROTOCOLS ... 138 20.3 WEBBROWSERS ... 138 20.4 MARKUPLANGUAGES ... 138 20.5 DEVELOPMENTENVIRONMENTS ... 138 21 PERFORMANCE TESTING ... 139
21.1 WHATIS PERFORMANCETESTING? ... 139
21.2 WHY PERFORMANCETESTING? ... 139
21.3 PERFORMANCE TESTING OBJECTIVES ... 140
21.4 PRE-REQUISITESFOR PERFORMANCE TESTING ... 140
21.5 PERFORMANCE REQUIREMENTS ... 141
22 PERFORMANCE TESTING PROCESS ... 143
22.1 PHASE 1 – REQUIREMENTS STUDY ... 144
22.2 PHASE 2 – TEST PLAN ... 145
22.3 PHASE 3 – TEST DESIGN ... 145
22.4 PHASE 4 –SCRIPTING ... 146
22.5 PHASE 5 – TEST EXECUTION ... 147
22.6 PHASE 6 – TEST ANALYSIS ... 147
22.7 PHASE 7 – PREPARATIONOF REPORTS ... 148
22.8 COMMON MISTAKESIN PERFORMANCE TESTING ... 149
22.9 BENCHMARKING LESSONS ... 149 23 TOOLS ... 152 23.1 LOADRUNNER 6.5 ... 152 23.2 WEBLOAD 4.5 ... 152 23.3 ARCHITECTURE BENCHMARKING ... 153 23.4 GENERAL TESTS ... 153 24 PERFORMANCE METRICS ... 155
24.1 CLIENT SIDE STATISTICS ... 155
26.5 ANALYZING RESULTS ... 160
26.6 CONCLUSION ... 160
27 STRESS TESTING ... 162
27.1 INTRODUCTIONTO STRESS TESTING ... 162
27.2 BACKGROUNDTO AUTOMATED STRESS TESTING ... 163
27.3 AUTOMATED STRESS TESTING IMPLEMENTATION ... 165
27.4 PROGRAMMABLE INTERFACES ... 165
27.5 GRAPHICAL USER INTERFACES ... 166
27.6 DATA FLOW DIAGRAM ... 166
27.7 TECHNIQUES USEDTO ISOLATE DEFECTS ... 167
28 TEST CASE COVERAGE ... 169
28.1 TEST COVERAGE ... 169
28.2 TESTCOVERAGEMEASURES ... 169
28.3 PROCEDURE-LEVEL TEST COVERAGE ... 170
28.4 LINE-LEVEL TEST COVERAGE ... 170
28.5 CONDITION COVERAGEAND OTHER MEASURES ... 170
28.6 HOW TEST COVERAGE TOOLS WORK ... 170
28.7 TEST COVERAGE TOOLSATA GLANCE ... 172
29 TEST CASE POINTS-TCP ... 173
29.1 WHATISA TEST CASE POINT (TCP) ... 173
29.2 CALCULATINGTHE TEST CASE POINTS: ... 173
1 Introduction to Software
1.1 Evolution of the Software Testing discipline
The effective functioning of modern systems depends on our ability to produce software in a cost-effective way. The term software engineering was first used at a 1968 NATO workshop in West Germany. It focused on the growing software crisis! Thus we see that the software crisis on quality, reliability, high costs etc. started way back when most of today’s software testers were not even born!
The attitude towards Software Testing underwent a major positive change in the recent years. In the 1950’s when Machine languages were used, testing is nothing but debugging. When in the 1960’s, compilers were developed, testing started to be considered a separate activity from debugging. In the 1970’s when the software engineering concepts were introduced, software testing began to evolve as a technical discipline. Over the last two decades there has been an increased focus on better, faster and cost-effective software. Also there has been a growing interest in software safety, protection and security and hence an increased acceptance of testing as a technical discipline and also a career choice!.
Now to answer, “What is Testing?” we can go by the famous definition of Myers, which says, “Testing is the process of executing a program with the intent of finding errors”
1.2 The Testing process and the Software Testing Life
Cycle
Every testing project has to follow the waterfall model of the testing process. The waterfall model is as given below
1.Test Strategy & Planning 2.Test Design
software development life cycle has become a necessity as part of the software quality assurance process. Right from the Requirements study till the implementation, there needs to betesting done on every phase. 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.
1.3 Broad Categories of Testing
Based on the V-Model mentioned above, we see that there are two categories of testing activities that can be done on software, namely,
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, design review, code review, walkthrough and audits. This type of testing is called Static Testing. When we test the software by executing and comparing the actual & expected results, it is called Dynamic Testing
1.4 Widely employed Types of Testing
From the V-model, we see that are various levels or phases of testing, namely, Unit testing, Integration testing, System testing, User Acceptance testing etc.
Let us see a brief definition on the widely employed types of testing.
Unit Testing: The testing done to a unit or to a smallest piece of software. Done to verify
if it satisfies its functional specification or its intended design structure.
Integration Testing: Testing which takes place as sub elements are combined (i.e.,
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 Requirement Study Low Level Design High Level Design Unit Testing Integration Testing SystemTesting User Acceptance Testing Production Verification Testing SDLC - STLC
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, which enables a customer to determine whether to accept the system or not.
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, memory, processor utilization) to ensure the system do not break unexpectedly
Load Testing: Load Testing, a subset of stress testing, 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.
1.5 The Testing Techniques
To perform these types of testing, there are two widely used testing techniques. The above said testing types are performed based on the following testing techniques.
Black-Box testing technique:
This technique is used for testing based solely on analysis of requirements (specification, user documentation.). Also known as functional testing.
This chapter covered the Introduction and basics of software testing mentioning about
Evolution of Software Testing
The Testing process and lifecycle
Broad categories of testing
Widely employed Types of Testing
2 Black Box and White Box testing
2.1 Introduction
Test Design refers to understanding the sources of test cases, test coverage, how to
develop and document test cases, and how to build and maintain test data. 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", so it doesn't explicitly
use knowledge of the internal structure. It is usually described as focusing on testing functional requirements. Synonyms for black-box include: behavioral, functional, opaque-box, and closed-box.
White-box test design allows one to peek inside the "box", and it focuses specifically on
using internal knowledge of the software to guide the selection of test data. It is used to detect errors by means of execution-oriented test cases. Synonyms for white-box include: structural, glass-box and clear-box.
While black-box and white-box are terms that are still in popular use, 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, but it's still discouraged. In practice, it hasn't proven useful to use a single test design method. One has to use a mixture of different methods so that they aren't hindered by the limitations of a particular one. Some call this "gray-box" or "translucent-box" test design, but others wish we'd stop talking about boxes altogether!!!
2.2 Black box testing
Black Box Testing is testing without knowledge of the internal workings of the item being
tested. For example, when black box testing is applied to software engineering, the tester would only know the "legal" inputs and what the expected outputs should be, but not how the program actually arrives at those outputs. It is because of this that black box
2.2.1.1 Black box testing - without user involvement
The so-called ``functionality testing'' is central to most testing exercises. Its primary objective is to assess whether the program does what it is supposed to do, i.e. what is specified in the requirements. There are different approaches to functionality testing. One is the testing of each program feature or function in sequence. The other is to test module by module, i.e. each function where it is called first.
The objective of volume tests is to find the limitations of the software by processing a huge amount of data. A volume test can uncover problems that are related to the efficiency of a system, e.g. incorrect buffer sizes, a consumption of too much memory space, or only show that an error message would be needed telling the user that the system cannot process the given amount of data.
During a stress test, the system has to process a huge amount of data or perform many function calls within a short period of time. A typical example could be to perform the same function from all workstations connected in a LAN within a short period of time (e.g. sending e-mails, or, in the NLP area, to modify a term bank via different terminals simultaneously).
The aim of recovery testing is to make sure to which extent data can be recovered after a system breakdown. 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, recovery testing is very important.
The notion of benchmark tests involves the testing of program efficiency. The efficiency of a piece of software strongly depends on the hardware environment and therefore benchmark tests always consider the soft/hardware combination. Whereas for most software engineers benchmark tests are concerned with the quantitative measurement of specific operations, some also consider user tests that compare the efficiency of different software systems as benchmark tests. In the context of this document, however, benchmark tests only denote operations that are independent of personal variables.
2.2.1.2 Black box testing - with user involvement
For tests involving users, methodological considerations are rare in SE literature. Rather, one may find practical test reports that distinguish roughly between field and laboratory tests. In the following only a rough description of field and laboratory tests will be given. E.g. Scenario Tests. The term ``scenario'' has entered software evaluation in the early 1990s . 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. In short it involves putting the system into its intended use by its envisaged type of user, performing a standardised task.
In field tests users are observed while using the software system at their normal working place. Apart from general usability-related aspects, field tests are particularly useful for assessing the interoperability of the software system, i.e. how the technical integration of the system works. Moreover, field tests are the only real means to elucidate problems of the organisational integration of the software system into existing procedures. Particularly in the NLP environment this problem has frequently been underestimated. A typical
example of the organisational problem of implementing a translation memory is the language service of a big automobile manufacturer, where the major implementation problem is not the technical environment, but the fact that many clients still submit their orders as print-out, that neither source texts nor target texts are properly organised and stored and, last but not least, individual translators are not too motivated to change their working habits.
Laboratory tests are mostly performed to assess the general usability of the system. Due to the high laboratory equipment costs laboratory tests are mostly only performed at big software houses such as IBM or Microsoft. Since laboratory tests provide testers with many technical possibilities, data collection and analysis are easier than for field tests.
2.3 Testing Strategies/Techniques
• Black box testing should make use of randomly generated inputs (only a test
range should be specified by the tester), 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), 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, syntax testing,
domain testing, logic testing, and state 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:
1. Clean tests against requirements.
2. Additional structural tests for branch coverage, as needed.
2.4 Black box testing Methods
2.4.1 Graph-based Testing Methods
• Black-box methods based on the nature of the relationships (links) among the
program objects (nodes), 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)
• 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, link weights are required execution times) 2.4.2 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:
1. If input condition specifies a range, one valid and two invalid equivalence classes are defined
2. If an input condition requires a specific value, one valid and two invalid equivalence classes are defined
3. If an input condition specifies a member of a set, one valid and one invalid equivalence class is defined
4. If an input condition is Boolean, one valid and one invalid equivalence class is defined
2.4.3 Boundary Value Analysis
• Black-box technique that focuses on the boundaries of the input domain rather
than its center
• BVA guidelines:
1. If input condition specifies a range bounded by values a and b, test cases should include a and b, values just above and just below a and b 2. If an input condition specifies and number of values, test cases should be
exercise the minimum and maximum numbers, as well as values just above and just below the minimum and maximum values
3. Apply guidelines 1 and 2 to output conditions, test cases should be designed to produce the minimum and maxim output reports
4. If internal program data structures have boundaries (e.g. size limitations), be certain to test the boundaries
2.4.4 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
2.4.5 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)
• Priorities for assessing tests using an orthogonal array 1. Detect and isolate all single mode faults 2. Detect all double mode faults
3. Multimode faults
2.4.6 Specialized Testing
• Graphical user interfaces
• Client/server architectures
• Documentation and help facilities
• Real-time systems
1. Task testing (test each time dependent task independently) 2. Behavioral testing (simulate system response to external events) 3. Intertask testing (check communications errors among tasks)
4. System testing (check interaction of integrated system software and hardware)
2.4.7 Advantages of Black Box Testing
• More effective on larger units of code than glass box testing
• Tester needs no knowledge of implementation, including specific programming
• 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
2.5 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. These terms are commonly used, yet everyone seems to have a different idea of what they mean.
Black box testing begins with a metaphor. Imagine you’re testing an electronics system. It’s housed in a black box with lights, switches, and dials on the outside. You must test it without opening it up, and you can’t see beyond its surface. You have to see if it works just by flipping switches (inputs) and seeing what happens to the lights and dials (outputs). This is black box testing. Black box software testing is doing the same thing, but with software. The actual meaning of the metaphor, however, depends on how you define the boundary of the box and what kind of access the “blackness” is blocking. An opposite test approach would be to open up the electronics system, see how the circuits are wired, apply probes internally and maybe even disassemble parts of it. By analogy, this is called white box testing,
To help understand the different ways that software testing can be divided between black box and white box techniques, consider the Five-Fold Testing System. It lays out five dimensions that can be used for examining testing:
1.People(who does the testing) 2. Coverage (what gets tested) 3. Risks (why you are testing) 4.Activities(how you are testing)
5. 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.
People: Who does the testing?
Some people know how software works (developers) and others just use it (users). Accordingly, any testing by users or other non-developers is sometimes called “black box” testing. Developer testing is called “white box” testing. The distinction here is based on what the person knows or can understand.
If we draw the box around the system as a whole, “black box” testing becomes another name for system testing. And testing the units inside the box becomes white box testing. This is one way to think about coverage. Another is to contrast testing that aims to cover all the requirements with testing that aims to cover all the code. These are the two most commonly used coverage criteria. Both are supported by extensive literature and commercial tools. Requirements-based testing could be called “black box” because it makes sure that all the customer requirements have been verified. Code-based testing is often called “white box” because it makes sure that all the code (the statements, paths, or decisions) is exercised.
Risks: Why are you testing?
Sometimes testing is targeted at particular risks. Boundary testing and other attack-based techniques are targeted at common coding errors. Effective security testing also requires a detailed understanding of the code and the system architecture. Thus, these techniques might be classified as “white box”. Another set of risks concerns whether the software will actually provide value to users. Usability testing focuses on this risk, and could be termed “black box.”
Activities: How do you test?
A common distinction is made between behavioral test design, which defines tests based on functional requirements, and structural test design, which defines tests based on the code itself. These are two design approaches. Since behavioral testing is based on external functional definition, it is often called “black box,” while structural testing—based on the code internals—is called “white box.” Indeed, this is probably the most commonly cited definition for black box and white box testing. Another activity-based distinction contrasts dynamic test execution with formal code inspection. In this case, the metaphor maps test execution (dynamic testing) with black box testing, and maps code inspection (static testing) with white box testing. We could also focus on the tools used. Some tool vendors refer to code-coverage tools as white box tools, and tools that facilitate applying inputs and capturing inputs—most notably GUI capture replay tools—as black box tools. Testing is then categorized based on the types of tools used.
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. They may be masked by fault tolerance or simply luck. Memory leaks and wild pointers are examples. Certain test techniques seek to make these kinds of problems more visible. Related techniques capture code history and stack information when faults occur, helping
faults of commission, indicating that part of the implementation is faulty. In order to fully test a software product both black and white box testing are required.
White box testing is much more expensive than black box testing. 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. The advice given is to start test planning with a black box test approach as soon as the specification is available. White box planning should commence as soon as all black box tests have been successfully passed, with the production of flowgraphs and determination of paths. The paths should then be checked against the black box test plan and any additional required test runs determined and applied.
The consequences of test failure at this stage may be very expensive. A failure of a white box test may result in a change which requires all black box testing to be repeated and the re-determination of the white box paths
To conclude, apart from the above described analytical methods of both glass and black box testing, there are further constructive means to guarantee high quality software end products. Among the most important constructive means are the usage of object-oriented programming tools, the integration of CASE tools, rapid prototyping, 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); system or requirements-based testing (coverage); usability testing (risk); or behavioral testing or capture replay automation (activities). White box testing, on the other hand, can sometimes describe developer-based testing (people); unit or code-coverage testing (coverage); boundary or security testing (risks); structural testing, inspection or code-coverage automation (activities); or testing based on probes, assertions, and logs (evaluation).
2.6 WHITE BOX TESTING
Software testing approaches that examine the program structure and derive test data from the program logic. 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.
Synonyms for white box testing
• Glass Box testing
• Structural testing
• Clear Box testing
• Open Box Testing
A typical rollout of a product is shown in figure 1 below.
The purpose of white box testing
Initiate a strategic initiative to build quality throughout the life cycle of a software product or service.
Provide a complementary function to black box testing. Perform complete coverage at the component level. Improve quality by optimizing performance.
Practices :
This section outlines some of the general practices comprising white-box testing process. In general, white-box testing practices have the
following considerations:
1. The allocation of resources to perform class and method analysis and to document and review the same.
basic set of execution paths. These are test cases that exercise basic set will execute every statement at least once.
1.1.1 Flow Graph Notation
A notation for representing control flow similar to flow charts and UML activity diagrams.
1.1.2 Cyclomatic Complexity
The cyclomatic complexity gives a quantitative measure of 4the logical complexity. This value gives the number of independent paths in the basis set, and an upper bound for the number of tests to ensure that each statement is executed at least once. An independent path is any path through a program that introduces at least one new set of
processing statements or a new condition (i.e., a new edge). Cyclomatic complexity provides upper bound for number of tests required to
guarantee coverage of all program statements.
1.2
Control Structure testing 1.2.1 Conditions TestingCondition testing aims to exercise all logical conditions in a program module. They may define:
• Relational expression: (E1 op E2), where E1 and E2 are
arithmetic expressions.
• Simple condition: Boolean variable or relational expression, possibly proceeded by a NOT operator.
• Compound condition: composed of two or more simple
conditions, Boolean operators and parentheses.
• Boolean expression : Condition without Relational expressions.
1.2.2 Data Flow Testing
Selects test paths according to the location of definitions and use of variables.
1.2.3 Loop Testing
Loops fundamental to many algorithms. Can define loops as simple, concatenated, nested, and unstructured.
Note that unstructured loops are not to be tested . rather, they are redesigned.
2 Design by Contract (DbC)
DbC is a formal way of using comments to incorporate specification information into the code itself. Basically, the code specification is expressed unambiguously using a formal language that describes the code's implicit contracts. These contracts specify such requirements as:
• Conditions that the client must meet before a method is invoked.
• 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.parasoft.com/products/jtract/index.htm] are used to perform this function.
Exception and error handling is checked thoroughly are simulating partial and complete fail-over by operating on error causing test vectors. Proper error recovery, notification and logging are checked against references to validate program design.
5 Transactions
Systems that employ transaction, local or distributed, may be validated to ensure that ACID (Atomicity, Consistency, Isolation, Durability). Each of the individual parameters is tested individually against a reference data set.
Transactions are checked thoroughly for partial/complete commits and rollbacks encompassing databases and other XA compliant transaction processors.
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
3 GUI Testing
What is GUI Testing?
GUI is the abbreviation for Graphic User Interface. It is absolutely essential that any application has to be user-friendly. The end user should be comfortable while using all the components on screen and the components should also perform their functionality with utmost clarity. Hence it becomes very essential to test the GUI components of any application. GUI Testing can refer to just ensuring that the look-and-feel of the application is acceptable to the user, or it can refer to testing the functionality of each and every component involved.
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.
3.1 Section 1 - Windows Compliance Testing
3.1.1 Application
Start Application by Double Clicking on its ICON. The Loading message should show the application name, version number, and a bigger pictorial representation of the icon. No Login is necessary. The main window of the application should have the same caption as the caption of the icon in Program Manager. Closing the application should result in an "Are you Sure" message box Attempt to start application twice. This should not be allowed - you should be returned to main window. Try to start the application twice as it is loading. On each window, if the application is busy, then the hour glass should be
displayed. If there is no hour glass, then some enquiry in progress message should be displayed. All screens should have a Help button (i.e.) F1 key should work the same.
If Window has a Minimize Button, click it. Window should return to an icon on the bottom of the screen. This icon should correspond to the Original Icon under Program Manager. Double Click the Icon to return the Window to its original size. The window caption for every application should have the name of the application and the window name - especially the error messages. These should be checked for spelling, English and clarity,
Never updateable fields should be displayed with black text on a gray background with a black label. All text should be left justified, followed by a colon tight to it. In a field that may or may not be updateable, the label text and contents changes from black to gray depending on the current status. List boxes are always white background with black text whether they are disabled or not. All others are gray.
In general, double-clicking is not essential. In general, everything can be done using both the mouse and the keyboard. All tab buttons should have a distinct letter.
3.1.2 Text Boxes
Move the Mouse Cursor over all Enterable Text Boxes. Cursor should change from arrow to Insert Bar. If it doesn't then the text in the box should be gray or non-updateable. Refer to previous page. Enter text into Box Try to overflow the text by typing to many characters - should be stopped Check the field width with capitals W. Enter invalid characters - Let-ters in amount fields, try strange characLet-ters like + , - * etc. in All fields. SHIFT and Arrow should Select Characters. Selection should also be possible with mouse. Double Click should select all text in box.
3.1.3 Option (Radio Buttons)
Left and Right arrows should move 'ON' Selection. So should Up and Down. Select with mouse by clicking.
3.1.4 Check Boxes
Clicking with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same.
3.1.5 Command Buttons
If Command Button leads to another Screen, 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. All Buttons except for OK and Cancel should have a letter Access to them. This is indicated by a letter underlined in the button text. Pressing ALT+Letter should activate the button. Make sure there is no duplication. Click each button once with the mouse - This should activate Tab to each button - Press SPACE - This should activate
Tab to each button - Press RETURN - This should activate The above are VERY IMPORTANT, and should be done for EVERY command Button. Tab to another type of control (not a command button). One button on the screen should be default (indicated by a thick black border). Pressing Return in ANY no command button control should activate it.
If there is a Cancel Button on the screen, then pressing <Esc> should activate it. If pressing the Command button results in uncorrectable data e.g. closing an action step, there should be a message phrased positively with Yes/No answers where Yes results in the completion of the action.
3.1.6 Drop Down List Boxes
Pressing the Arrow should give list of options. This List may be scrollable. You should not be able to type text in the box. Pressing a letter should bring you to the first item in the list with that start with that letter. Pressing ‘Ctrl - F4’ should open/drop down the list box.
Spacing should be compatible with the existing windows spacing (word etc.). Items should be in alphabetical order with the exception of blank/none, which is at the top or the bottom of the list box. Drop down with the item selected should be display the list with the selected item on the top. Make sure only one space appears, shouldn't have a blank line at the bottom.
3.1.7 Combo Boxes
Should allow text to be entered. Clicking Arrow should allow user to choose from list
3.1.8 List Boxes
Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys. Pressing a letter should take you to the first item in the list starting with that letter. If there is a 'View' or 'Open' button besides the list box then double click-ing on a line in the List Box, should act in the same way as selectclick-ing and item in the list box, then clicking the command button. Force the scroll bar to appear, make sure all the data can be seen in the box.
3.2 Section 2 - Screen Validation Checklist
3.2.1 Aesthetic Conditions:
1. Is the general screen background the correct color? 2. Are the field prompts the correct color?
3. Are the field backgrounds the correct color?
4. In read-only mode, are the field prompts the correct color? 5. In read-only mode, are the field backgrounds the correct color? 6. Are all the screen prompts specified in the correct screen font? 7. Is the text in all fields specified in the correct screen font? 8. Are all the field prompts aligned perfectly on the screen? 9. Are all the field edit boxes aligned perfectly on the screen? 10. Are all group boxes aligned correctly on the screen? 11. Should the screen be resizable?
12. Should the screen be allowed to minimize? 13. Are all the field prompts spelt correctly?
3.2.2 Validation Conditions:
1. Does a failure of validation on every field cause a sensible user error message? 2. Is the user required to fix entries, which have failed validation tests?
3. Have any fields got multiple validation rules and if so are all rules being applied? 4. If the user enters an invalid value and clicks on the OK button (i.e. does not TAB
off the field) is the invalid entry identified and highlighted correctly with an error message?
5. Is validation consistently applied at screen level unless specifically required at field level?
6. For all numeric fields check whether negative numbers can and should be able to be entered.
7. For all numeric fields check the minimum and maximum values and also some mid-range values allowable?
8. 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?
9. Do all mandatory fields require user input?
10. 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.)
3.2.3 Navigation Conditions:
1. Can the screen be accessed correctly from the menu? 2. Can the screen be accessed correctly from the toolbar?
3. Can the screen be accessed correctly by double clicking on a list control on the previous screen?
4. Can all screens accessible via buttons on this screen be accessed correctly? 5. Can all screens accessible by double clicking on a list control be accessed
correctly?
6. Is the screen modal? (i.e.) Is the user prevented from accessing other functions when this screen is active and is this correct?
7. Can a number of instances of this screen be opened at the same time and is this correct?
3.2.4 Usability Conditions:
1. Are all the dropdowns on this screen sorted correctly? Alphabetic sorting is the default unless otherwise specified.
2. Is all date entry required in the correct format?
3. Have all pushbuttons on the screen been given appropriate Shortcut keys? 4. Do the Shortcut keys work correctly?
5. Have the menu options that apply to your screen got fast keys associated and should they have?
6. Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
7. Are all read-only fields avoided in the TAB sequence? 8. Are all disabled fields avoided in the TAB sequence?
9. Can the cursor be placed in the microhelp text box by clicking on the text box with the mouse?
10. Can the cursor be placed in read-only fields by clicking in the field with the mouse?
11. Is the cursor positioned in the first input field or control when the screen is opened?
12. Is there a default button specified on the screen? 13. Does the default button work correctly?
14. When an error message occurs does the focus return to the field in error when the user cancels it?
15. When the user Alt+Tab's to another application does this have any impact on the screen upon return to the application?
16. 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
3.2.5 Data Integrity Conditions:
1. Is the data saved when the window is closed by double clicking on the close box?
2. Check the maximum field lengths to ensure that there are no truncated characters?
3. 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.
4. Check maximum and minimum field values for numeric fields?
5. 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? 6. 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.)
7. 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.
3.2.6 Modes (Editable Read-only) Conditions:
1. Are the screen and field colors adjusted correctly for read-only mode? 2. Should a read-only mode be provided for this screen?
3. Are all fields and controls disabled in read-only mode?
6. In drop down list boxes, assure that the list and each entry in the list can be accessed via appropriate key / hot key combinations.
7. Ensure that duplicate hot keys do not exist on each screen
8. 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"
9. Assure that the cancel button functions the same as the escape key.
10. Assure that the Cancel button operates, as a Close button when changes have been made that cannot be undone.
11. 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.
12. When a command button is used sometimes and not at other times, assures that it is grayed out when it should not be used.
13. Assure that OK and Cancel buttons are grouped separately from other command buttons.
14. Assure that command button names are not abbreviations.
15. Assure that all field labels/names are not technical labels, but rather are names meaningful to system users.
16. Assure that command buttons are all of similar size and shape, and same font & font size.
17. Assure that each command button can be accessed via a hot key combination. 18. Assure that command buttons in the same window/dialog box do not have
duplicate hot keys.
19. 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
20. Assure that focus is set to an object/button, which makes sense according to the function of the window/dialog box.
21. Assure that all option buttons (and radio buttons) names are not abbreviations. 22. Assure that option button names are not technical labels, but rather are names
meaningful to system users.
23. If hot keys are used to access option buttons, assure that duplicate hot keys do not exist in the same window/dialog box.
24. Assure that option box names are not abbreviations.
25. Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "Group Box"
26. Assure that the Tab key sequence, which traverses the screens, does so in a logical way.
27. Assure consistency of mouse actions across windows.
28. Assure that the color red is not used to highlight active objects (many individuals are red-green color blind).
29. 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).
30. Assure that the screen/window does not have a cluttered appearance 31. Ctrl + F6 opens next tab within tabbed window
32. Shift + Ctrl + F6 opens previous tab within tabbed window
34. Tabbing will go onto the 'Continue' button if on last field of last tab within tabbed window
35. Tabbing will go onto the next editable field in the window 36. Banner style & size & display exact same as existing windows
37. If 8 or less options in a list box, display all options on open of list box - should be no need to scroll
38. Errors on continue will cause user to be returned to the tab and the focus should be on the field causing the error. (i.e the tab is opened, highlighting the field with the error on it)
39. Pressing continue while on the first tab of a tabbed window (assuming all fields filled correctly) will not open all the tabs.
40. On open of tab focus will be on first editable field 41. All fonts to be the same
42. Alt+F4 will close the tabbed window and return you to main screen or previous screen (as appropriate), generating "changes will be lost" message if necessary. 43. Microhelp text for every enabled field & button
44. Ensure all fields are disabled in read-only mode 45. Progress messages on load of tabbed screens 46. Return operates continue
47. If retrieve on load of tabbed window fails window should not open
3.3 Specific Field Tests
3.3.1 Date Field Checks
1. Assure that leap years are validated correctly & do not cause errors/miscalculations.
2. Assure that month code 00 and 13 are validated correctly & do not cause errors/miscalculations.
3. Assure that 00 and 13 are reported as errors.
4. Assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations.
5. Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations.
6. Assure that Feb. 30 is reported as an error.
7. Assure that century change is validated correctly & does not cause errors/ miscalculations.
8. Include value zero in all calculations. 9. Include at least one in-range value.
10. Include maximum and minimum range values.
11. Include out of range values above the maximum and below the minimum. 12. Assure that upper and lower values in ranges are handled correctly.
3.3.3 Alpha Field Checks
1. Use blank and non-blank data. 2. Include lowest and highest values. 3. Include invalid characters & symbols. 4. Include valid characters.
5. Include data items with first position blank. 6. Include data items with last position blank.
3.4 Validation Testing - Standard Actions
3.4.1 Examples of Standard Actions - Substitute your specific
commands
Add
View
Change
Delete
Continue - (i.e. continue saving changes or additions)
Add
View
Change
Delete
Cancel - (i.e. abandon changes or additions)
Fill each field - Valid data
Fill each field - Invalid data
Different Check Box / Radio Box combinations
Scroll Lists / Drop Down List Boxes
Help
Fill Lists and Scroll
Tab
Tab Sequence
Shift Tab
3.4.2 Shortcut keys / Hot Keys
Note: The following keys are used in some windows applications, and are
included
as
a
guide.
Key
No Modifier
Shift
CTRL
ALT
F1
Help
Enter
Help
Mode
N/A
N/A
F2
N/A
N/A
N/A
N/A
F3
N/A
N/A
N/A
N/A
F4
N/A
N/A
Close
Document /
Child window.
Close
Application.
F5
N/A
N/A
N/A
N/A
F6
N/A
N/A
N/A
N/A
F7
N/A
N/A
N/A
N/A
F8
Toggle extend
mode,
if
supported.
Toggle Add
mode,
if
supported.
N/A
N/A
F9
N/A
N/A
N/A
N/A
F10
Toggle menu bar
activation.
N/A
N/A
N/A
F11, F12 N/A
N/A
N/A
N/A
Tab
Move to next
active/editable
field.
Move
to
previous
active/editable
field.
Move to next
open Document
or
Child
window.
Switch
to
previously used
application.
(Holding down
3.4.3 Control Shortcut Keys
Key
Function
CTRL + Z
Undo
CTRL + X
Cut
CTRL + C
Copy
CTRL + V
Paste
CTRL + N
New
CTRL + O
Open
CTRL + P
CTRL + S
Save
CTRL + B
Bold*
CTRL + I
Italic*
CTRL + U
Underline*
* These shortcuts are suggested for text formatting applications, in the context for
which they make sense. Applications may use other modifiers for these
operations.
4 Regression Testing
4.1 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.
− Regression testing is a normal part of the program development process. Test
department coders develop code test scenarios and exercises that will test new units of code after they have been written.
− Before a new version of a software product is released, the old test cases are run against the new version to make sure that all the old capabilities still work. 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.
−
The selective retesting of a software system that has been modified to ensurethat 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. 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.
4.2 Test Execution
Test Execution is the heart of the testing process. Each time your application changes, you will want to execute the relevant parts of your test plan in order to locate defects and assess quality.
4.2.1 Create Test Cycles
During this stage you decide the subset of tests from your test database you want to execute.
Usually you do not run all the tests at once. At different stages of the quality assurance process, you need to execute different tests in order to address specific goals. A related group of tests is called a test cycle, 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. You can run the cycle each time a new build is ready, 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. This test cycle includes tests that check that module in depth.
To decide which test cycles to build, refer to the testing goals you defined at the
beginning of the process. Also consider issues such as the current state of the application and whether new functions have been added or modified.
Following are examples of some general categories of test cycles to consider:
•
sanity cycle checks the entire system at a basic level (breadth, rather than depth)to see that it is functional and stable. This cycle should include basic-level tests containing mostly positive checks.
•
normal cycle tests the system a little more in depth than the sanity cycle. This cyclecan group medium-level tests, containing both positive and negative checks.
•
advanced cycle tests both breadth and depth. This cycle can be run when moretime is available for testing. The tests in the cycle cover the entire application (breadth), and also test advanced options in the application (depth).
•
regression cycle tests maintenance builds. The goal of this type of cycle is to verifythat a change to one part of the software did not break the rest of the application. A regression cycle includes sanity-level tests for testing the entire software, as well as in-depth tests for the specific area of the application that was modified.
4.2.2 Run Test Cycles (Automated & Manual Tests)
Once you have created cycles that cover your testing objectives, you begin executing the tests in the cycle. You perform manual tests using the test steps. Testing Tools executes automated tests for you. A test cycle is complete only when all tests-automatic and
manual-have been run.
−
With Manual Test Execution you follow the instructions in the test steps of each test. You use the application, enter input, compare the application output with the expected output, and log the results. For each test step you assign either pass or fail status.− During Automated Test Execution you create a batch of tests and launch the
entire batch at once. Testing Tools runs the tests one at a time. It then imports results, providing outcome summaries for each test.
4.2.3 Analyze Test Results
After every test run one analyze and validate the test results. And have to identify all the failed steps in the tests and to determine whether a bug has been detected, or if the expected result needs to be updated.
4.3 Change Request
4.3.1 Initiating a Change Request
A user or developer wants to suggest a modification that would improve an existing application, notices a problem with an application, or wants to recommend an
enhancement. Any major or minor request is considered a problem with an application and will be entered as a change request.
4.3.2 Type of Change Request
Bug the application works incorrectly or provides incorrect information. (for example, a
letter is allowed to be entered in a number field)
Change a modification of the existing application. (for example, sorting the files
alphabetically by the second field rather than numerically by the first field makes them easier to find)
Enhancement new functionality or item added to the application. (for example, a new
report, a new field, or a new button)
phases of the testing process.
−
Information about bugs must be detailed and organized in order to schedule bugfixes and determine software release dates.
Bug Tracking involves two main stages: reporting and tracking.
4.4.1 Report Bugs
Once you execute the manual and automated tests in a cycle, you report the bugs (or defects) that you detected. The bugs are stored in a database so that you can manage them and analyze the status of your application.
When you report a bug, you record all the information necessary to reproduce and fix it. You also make sure that the QA and development personnel involved in fixing the bug are notified.
4.4.2 Track and Analyze Bugs
The lifecycle of a bug begins when it is reported and ends when it is fixed, verified, and closed.
−
First you report New bugs to the database, and provide all necessaryinformation to reproduce, fix, and follow up the bug.
−
The Quality Assurance manager or Project manager periodically reviews allNew bugs and decides which should be fixed. These bugs are given the status Open and are assigned to a member of the development team.
−
Software developers fix the Open bugs and assign them the status Fixed.−
QA personnel test a new build of the application. If a bug does not reoccur, it is Closed. If a bug is detected again, it is reopened.Communication is an essential part of bug tracking; 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.
The number of open or fixed bugs is a good indicator of the quality status of your
application. You can use data analysis tools such as re-ports and graphs in interpret bug data.
4.5 Traceability Matrix
A traceability matrix is created by associating requirements with the products that satisfy them. Tests are associated with the requirements on which they are based and the
product tested to meet the requirement. Below is a simple traceability matrix structure. There can be more things included in a traceability matrix than shown below. Traceability requires unique identifiers for each requirement and product. Numbers for products are established in a configuration management (CM) plan.
Traceability ensures completeness, that all lower level requirements derive from higher level requirements, and that all higher level requirements are allocated to lower level requirements. Traceability is also used in managing change and provides the basis for test planning.
SAMPLE TRACEABILITY MATRIX
A traceability matrix is a report from the requirements database or repository. The examples below show traceability between user and system requirements. User requirement identifiers begin with "U" and system requirements with "S."
In addition to traceability matrices, other reports are necessary to manage requirements. What goes into each report depends on the information needs of those receiving the report(s). Determine their information needs and document the information that will be associated with the requirements when you set up your requirements database or repository
5 Phases of Testing
5.1 Introduction
The Primary objective of testing effort is to determine the conformance to requirements specified in the contracted documents. The integration of this code with the internal code is the important objective. Goal is to evaluate the system as a whole, not its parts
Techniques can be structural or functional.
Techniques can be used in any stage that tests the system as a whole (System testing ,Acceptance Testing, Unit testing, Installation, etc.)
5.2 Types and Phases of Testing
SDLC Document QA Document
Software Requirement Specification Requirement Checklist
Design Document Design Checklist
Functional Specification Functional Checklist
Design Document & Functional Specs Unit Test Case Documents
Design Document & Functional Specs Integration Test Case Documents
Design Document & Functional Specs System Test Case Documents
Unit / System / Integration Test Case Documents Regression Test Case Documents
Functional Specs, Performance Criteria Performance Test Case Documents
Software Requirement Specification, Unit / System / Integration / Regression / Performance Test Case Documents
User Acceptance Test Case Documents.
5.3 The “V”Model
Requirements
Specification
Architecture
Detailed Design Unit Testing
Integration Testing System Testing
Acceptance Testing
Requirement Study Software Requirement Requirement Checklist Software
Requirement Specification Functional Functional Specification Functional
Specification Architecture Design Architecture
Design Detailed Design Document Coding
Functional
Specification Unit Test Case Documents Design
Document Functional Specification
Unit Test Case System Test Case Document Integration Test Case Unit/Integratio n/System Test Regression Test Case Functional Specification Performance Performance Test Cases and Software
Requirement Regression
Test Case Performance Test Cases and
User Acceptance Test Case
Regression Round 3 Performance Testing Regression Round 2 Regression Round 1 Design Review Architectur e Review Specification Review Requirement s Review Requirement Specification Architecture Detailed Unit Testing Integration Testing System Testing Code Code Walkthrough
