Scribd
Upload
11 views4 pages

Here Is A Complete and Clear Note For Unit 3

Unit 3 – Software Testing covers various testing procedures, including path testing, testing issues, data flow testing, testing tracking, types of testing (stress, load, failover), performance testing techniques, and test case organization. It outlines definitions, advantages, disadvantages, and examples for each topic, emphasizing the importance of systematic testing and effective tracking. Tools and practices for improving test coverage and defect identification are also discussed.

Uploaded by

LOVE INDIA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views4 pages

Here Is A Complete and Clear Note For Unit 3

Unit 3 – Software Testing covers various testing procedures, including path testing, testing issues, data flow testing, testing tracking, types of testing (stress, load, failover), performance testing techniques, and test case organization. It outlines definitions, advantages, disadvantages, and examples for each topic, emphasizing the importance of systematic testing and effective tracking. Tools and practices for improving test coverage and defect identification are also discussed.

Uploaded by

LOVE INDIA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Here is a complete and clear note for Unit 3 – Software Testing, with definitions,

advantages, disadvantages, and examples added for each topic:

UNIT 3 – SOFTWARE TESTING

1. Testing Procedures and Path Testing

Testing Procedures

Testing procedures are step-by-step instructions or guidelines that testers follow to ensure
the software is tested systematically and effectively.

Path Testing

Path testing is a white-box testing technique that ensures all possible execution paths in
the code are tested at least once.

• Focuses on logical paths in the control flow graph.

• Helps detect unreachable code, loops, and conditional errors.

Example:
In an if-else block, path testing ensures both the if and else conditions are tested.

2. Testing Issues – Definition, Advantages, and Disadvantages

Definition:

Testing issues are challenges faced during the testing phase such as incomplete
requirements, time pressure, tool unavailability, or unclear test data.

Advantages of Testing:

• Identifies and helps fix defects early.

• Improves quality and reliability.

• Ensures requirement coverage.

Disadvantages:

• Can be time-consuming.

• May require costly tools and environments.

• Complex systems may lead to missed defects.


3. Data Flow Testing

Definition:

A white-box testing method that focuses on how data (variables) flow through the program,
from their definition to their usage.

Key Concepts:

• Def (Definition) – Assigning value to a variable.

• Use – Using the variable in calculations or conditions.

• DU Pair – A pair of definition and use of the same variable.

Example:

int a = 5; // Definition

b = a + 2; // Use

4. Testing Tracking

Definition:

Test tracking involves monitoring and recording the progress of test activities, defects,
execution status, and coverage.

Importance:

• Helps track test case progress.

• Improves accountability and planning.

• Supports defect analysis and reporting.

Tools Used:

• JIRA, TestLink, HP ALM, Bugzilla.

5. Types of Testing: Stress, Load, Failover

Type Definition Purpose Example

Tests system beyond its Checks how it behaves Simulate 10,000+ users at
Stress
capacity under pressure once
Type Definition Purpose Example

Tests system under Checks performance 500 users login


Load
expected load during peak load simultaneously

Tests backup system when Switch from Server A to B


Failover Ensures high availability
the primary fails during failure

6. Testing Performance Techniques

Definition:

Performance testing ensures that software performs well under expected workload, in
terms of speed, scalability, and stability.

Techniques:

• Load Testing – Normal user load.

• Stress Testing – Extreme load.

• Spike Testing – Sudden surge in users.

• Endurance Testing – Long-term usage.

• Volume Testing – Large amount of data.

Tools:

• JMeter, LoadRunner, NeoLoad, BlazeMeter.

7. Test Case Organization

Definition:

Organizing test cases in a structured and manageable way for easy tracking, execution, and
updating.

Key Practices:

• Use folders/modules (e.g., Login, Registration).

• Assign priority (High, Medium, Low).

• Use naming conventions (e.g., TC_Login_001).

• Maintain traceability to requirements.


• Use test management tools.

Benefits:

• Improves test coverage.

• Simplifies execution and reporting.

• Enables faster defect identification.

Would you like this as a PDF or Word document for easy revision or printing?

You might also like