Areas of Testing:

Areas of Testing:

§  Black Box Testing

§  White Box Testing

§  Gray Box Testing

Black Box Testing

§  Test the correctness of the functionality with the help of Inputs and Outputs.

§  User doesn’t require the knowledge of software code.

§  Black box testing is also called as Functionality Testing.

It attempts to find errors in the following categories:

§  Incorrect or missing functions.

§  Interface errors.

§  Errors in data structures or external data base access.

§  Behavior or performance based errors.

§  Initialization or termination errors.

Approach:

Equivalence Class:

• For each piece of the specification, generate one or more equivalence Class
• Label the classes as “Valid” or “Invalid”
• Generate one test case for each Invalid Equivalence class
• Generate a test case that covers as many Valid Equivalence Classes as possible

An input condition for Equivalence Class

• A specific numeric value
• A range of values
• A set of related values
• A Boolean condition

Equivalence classes can be defined using the following guidelines

• If an input condition specifies a range, one valid and two invalid equivalence class are defined.
• If an input condition requires a specific value, one valid and two invalid equivalence classes are defined.
• If an input condition specifies a member of a set, one valid and one invalid equivalence classes are defined.
• If an input condition is Boolean, one valid and one invalid classes are defined.

Boundary Value Analysis

• Generate test cases for the boundary values.
• Minimum Value, Minimum Value + 1, Minimum Value -1
• Maximum Value, Maximum Value + 1, Maximum Value - 1

Error Guessing.

• Generating test cases against to the specification.

White Box Testing

§ Testing the Internal program logic

§ White box testing is also called as Structural testing.

§ User does require the knowledge of software code.

Purpose

§ Testing all loops

§ Testing Basis paths

§ Testing conditional statements

§ Testing data structures

§ Testing Logic Errors

§ Testing Incorrect assumptions

Structure = 1 Entry + 1 Exit with certain Constraints, Conditions and Loops.

       Logic Errors and incorrect assumptions most are likely to be made while coding for

       “special cases”. Need to ensure these execution paths are tested.

Approach

Basic Path Testing (Cyclomatic Complexity(Mc Cabe Method)

• Measures the logical complexity of a procedural design.
• Provides flow-graph notation to identify independent paths of processing
• Once paths are identified - tests can be developed for - loops, conditions
• Process guarantees that every statement will get executed at least once.

     Structure Testing:

• Condition Testing

All logical conditions  contained in the program module should be tested.

• Data Flow Testing

       Selects test paths according to the location of definitions and use of variables.

• Loop Testing

¨      Simple Loops

¨      Nested Loops

¨      Concatenated Loops

¨      Unstructured Loops

Gray Box Testing.

§  It is just a combination of both Black box & white box testing.

§  It is platform independent and language independent.

§  Used to test embedded systems.

§  Functionality and behavioral parts are tested.

§  Tester should have the knowledge of both the internals and externals of the function

§  If you know something about how the product works on the inside, you can test it better from the outside.

Gray box testing is especially important with Web and Internet applications, because the Internet is built around loosely integrated components that connect via relatively well-defined interfaces. Unless you understand the architecture of the Net, your testing will be skin deep.

1.6 Installation & Maintenance

Installation

• File conversion
• New system becomes operational
• Staff training

Maintenance

• Corrective maintenance à A type of maintenance performed to correct a defect
• Perfective maintenance  à    Reengineering include enhancement
• Adaptive maintenance  à  To change software so that it will work in an altered environment, such as when an operating system, hardware platform, compiler, software library or database structure changes

Table format of all the phases in SDLC:

PHASE	INPUT	OUTPUT
Analysis	BRS	FRS and SRS
Design	FRS and SRS	Design Doc
Coding	Design Doc	.exe File/Application/Website
Testing	All the above Doc’s	Defect Report