Module 1: Software Testing Fundamentals

Introduction to Software Testing

Understand what software testing is, why it's important, and how it fits into the software development process

Software Testing & QA Specialist

What is Software Testing?

Software testing is the process of evaluating and verifying that a software application or system does what it is supposed to do. It involves executing software components using a manual or automated approach to evaluate one or more properties of interest.

Why is Software Testing Important?

•Quality Assurance: Ensures software meets quality standards
•Bug Detection: Identifies defects before production
•Cost Reduction: Early bug detection saves money
•User Satisfaction: Delivers reliable software to users
•Risk Mitigation: Reduces business and technical risks
•Compliance: Meets regulatory and industry standards

Software Testing Principles

•Testing shows presence of defects
•Exhaustive testing is impossible
•Early testing saves time and money
•Defects cluster together
•Beware of the pesticide paradox
•Testing is context dependent
•Absence of errors is a fallacy

Testing vs Debugging

Code Example

// Testing vs Debugging
// Testing: Finding defects
function testLogin() {
    const result = login("user", "password");
    assert(result.success === true);
    assert(result.message === "Login successful");
}

// Debugging: Fixing defects
function login(username, password) {
    // Bug: Missing validation
    if (!username || !password) {
        return { success: false, message: "Invalid credentials" };
    }
    
    // Fixed: Added proper validation
    if (username.length < 3) {
        return { success: false, message: "Username too short" };
    }
    
    return { success: true, message: "Login successful" };
}

Swipe to see more code

// Testing vs Debugging
// Testing: Finding defects
function testLogin() {
    const result = login("user", "password");
    assert(result.success === true);
    assert(result.message === "Login successful");
}

// Debugging: Fixing defects
function login(username, password) {
    // Bug: Missing validation
    if (!username || !password) {
        return { success: false, message: "Invalid credentials" };
    }
    
    // Fixed: Added proper validation
    if (username.length < 3) {
        return { success: false, message: "Username too short" };
    }
    
    return { success: true, message: "Login successful" };
}

Scroll

🎯 Practice Exercise

Test your understanding of this topic:

I understand the basic concepts covered in this topicI can apply the concepts in practical scenariosI'm ready to move to the next topic

Software Development Life Cycle (SDLC)

Learn about different SDLC models and how testing integrates into each phase

Content by: Kaushal Gajipara

Software Testing & QA Specialist

Connect

SDLC Phases

•Planning: Requirements gathering and analysis
•Design: System and software design
•Implementation: Coding and development
•Testing: Quality assurance and validation
•Deployment: Release to production
•Maintenance: Ongoing support and updates

SDLC Models

•Waterfall: Sequential, linear approach
•Agile: Iterative, collaborative approach
•V-Model: Testing integrated with development
•Spiral: Risk-driven, iterative approach
•DevOps: Continuous integration and deployment

Testing in Different SDLC Models

Code Example

// Waterfall Model Testing
Requirements → Design → Implementation → Testing → Deployment

// V-Model Testing
Requirements ←→ Acceptance Testing
Design ←→ System Testing
Implementation ←→ Integration Testing
Unit Testing ←→ Unit Code

// Agile Model Testing
Sprint Planning → Development → Testing → Review → Retrospective
(Continuous testing throughout each sprint)

// DevOps Model Testing
Code → Build → Test → Deploy → Monitor
(Continuous testing in CI/CD pipeline)

Swipe to see more code

// Waterfall Model Testing
Requirements → Design → Implementation → Testing → Deployment

// V-Model Testing
Requirements ←→ Acceptance Testing
Design ←→ System Testing
Implementation ←→ Integration Testing
Unit Testing ←→ Unit Code

// Agile Model Testing
Sprint Planning → Development → Testing → Review → Retrospective
(Continuous testing throughout each sprint)

// DevOps Model Testing
Code → Build → Test → Deploy → Monitor
(Continuous testing in CI/CD pipeline)

Scroll

🎯 Practice Exercise

Test your understanding of this topic:

I understand the basic concepts covered in this topicI can apply the concepts in practical scenariosI'm ready to move to the next topic

Testing Life Cycle (STLC)

Understand the systematic approach to testing through the Testing Life Cycle

Content by: Paras Dadhania

Software Testing & QA Specialist

Connect

STLC Phases

•Test Planning: Define testing strategy and approach
•Test Analysis: Analyze requirements and create test cases
•Test Design: Create detailed test scenarios
•Test Implementation: Prepare test environment and data
•Test Execution: Run tests and log results
•Test Closure: Analyze results and create reports

Test Planning Activities

•Define test objectives and scope
•Identify test deliverables
•Estimate effort and resources
•Define test environment requirements
•Create test schedule and milestones
•Identify risks and mitigation strategies

Test Analysis and Design

Code Example

// Test Analysis Example
// Requirements Analysis
REQ-001: User should be able to login with valid credentials
REQ-002: User should be redirected to dashboard after successful login
REQ-003: User should see error message for invalid credentials

// Test Case Design
TC-001: Valid Login Test
- Input: username="testuser", password="testpass"
- Expected: Login successful, redirect to dashboard

TC-002: Invalid Username Test
- Input: username="invalid", password="testpass"
- Expected: Error message "Invalid username or password"

TC-003: Invalid Password Test
- Input: username="testuser", password="wrongpass"
- Expected: Error message "Invalid username or password"

// Test Scenario Design
Scenario 1: Happy Path Login
- Given: User is on login page
- When: User enters valid credentials
- Then: User should be logged in successfully

Scenario 2: Invalid Credentials
- Given: User is on login page
- When: User enters invalid credentials
- Then: User should see error message

Swipe to see more code

// Test Analysis Example
// Requirements Analysis
REQ-001: User should be able to login with valid credentials
REQ-002: User should be redirected to dashboard after successful login
REQ-003: User should see error message for invalid credentials

// Test Case Design
TC-001: Valid Login Test
- Input: username="testuser", password="testpass"
- Expected: Login successful, redirect to dashboard

TC-002: Invalid Username Test
- Input: username="invalid", password="testpass"
- Expected: Error message "Invalid username or password"

TC-003: Invalid Password Test
- Input: username="testuser", password="wrongpass"
- Expected: Error message "Invalid username or password"

// Test Scenario Design
Scenario 1: Happy Path Login
- Given: User is on login page
- When: User enters valid credentials
- Then: User should be logged in successfully

Scenario 2: Invalid Credentials
- Given: User is on login page
- When: User enters invalid credentials
- Then: User should see error message

Scroll

🎯 Practice Exercise

Test your understanding of this topic:

I understand the basic concepts covered in this topicI can apply the concepts in practical scenariosI'm ready to move to the next topic

Types of Testing

Learn about different types of testing and when to use each

Content by: Yash Sanghavi

Software Testing & QA Specialist

Connect

Functional Testing

•Unit Testing: Testing individual components
•Integration Testing: Testing component interactions
•System Testing: Testing complete system
•Acceptance Testing: User acceptance validation
•Smoke Testing: Basic functionality verification
•Sanity Testing: Quick validation after changes

Non-Functional Testing

•Performance Testing: Speed and responsiveness
•Load Testing: Normal expected load
•Stress Testing: Beyond normal capacity
•Security Testing: Vulnerability assessment
•Usability Testing: User experience validation
•Compatibility Testing: Cross-platform testing

Testing Types by Approach

Code Example

// Manual Testing
// Human tester executes test cases manually
function manualLoginTest() {
    // 1. Open browser
    // 2. Navigate to login page
    // 3. Enter username
    // 4. Enter password
    // 5. Click login button
    // 6. Verify dashboard appears
    // 7. Log results
}

// Automated Testing
// Test scripts execute automatically
describe('Login Functionality', () => {
    test('should login with valid credentials', () => {
        const result = login('user', 'pass');
        expect(result.success).toBe(true);
    });
    
    test('should fail with invalid credentials', () => {
        const result = login('user', 'wrong');
        expect(result.success).toBe(false);
    });
});

// Black Box Testing
// Testing without knowledge of internal code
function testUserRegistration() {
    // Input: User data
    // Expected: User created successfully
    // Don't need to know internal implementation
}

// White Box Testing
// Testing with knowledge of internal code
function testDatabaseConnection() {
    // Need to know database implementation
    // Test internal database logic
    // Verify SQL queries work correctly
}

Swipe to see more code

// Manual Testing
// Human tester executes test cases manually
function manualLoginTest() {
    // 1. Open browser
    // 2. Navigate to login page
    // 3. Enter username
    // 4. Enter password
    // 5. Click login button
    // 6. Verify dashboard appears
    // 7. Log results
}

// Automated Testing
// Test scripts execute automatically
describe('Login Functionality', () => {
    test('should login with valid credentials', () => {
        const result = login('user', 'pass');
        expect(result.success).toBe(true);
    });
    
    test('should fail with invalid credentials', () => {
        const result = login('user', 'wrong');
        expect(result.success).toBe(false);
    });
});

// Black Box Testing
// Testing without knowledge of internal code
function testUserRegistration() {
    // Input: User data
    // Expected: User created successfully
    // Don't need to know internal implementation
}

// White Box Testing
// Testing with knowledge of internal code
function testDatabaseConnection() {
    // Need to know database implementation
    // Test internal database logic
    // Verify SQL queries work correctly
}

Scroll

🎯 Practice Exercise

Test your understanding of this topic:

I understand the basic concepts covered in this topicI can apply the concepts in practical scenariosI'm ready to move to the next topic

Testing Levels & Phases

Understand different testing levels and their purposes in the testing pyramid

Content by: Paras Dadhania

Software Testing & QA Specialist

Connect

Testing Pyramid Levels

•Unit Testing: Individual components (70%)
•Integration Testing: Component interactions (20%)
•End-to-End Testing: Complete user workflows (10%)

Unit Testing

•Tests individual functions or methods
•Fastest to execute
•Highest number of tests
•Developers typically write these
•Catches bugs early in development

Integration Testing

•Tests interaction between components
•Medium execution speed
•Moderate number of tests
•QA team typically writes these
•Catches interface and communication bugs

Testing Level Examples

Code Example

// Unit Testing Example
function calculateTotal(items) {
    return items.reduce((sum, item) => sum + item.price, 0);
}

// Unit test
test('calculateTotal should return correct sum', () => {
    const items = [
        { price: 10 },
        { price: 20 },
        { price: 30 }
    ];
    expect(calculateTotal(items)).toBe(60);
});

// Integration Testing Example
// Test how components work together
test('user registration flow', () => {
    // 1. User submits form
    // 2. Validation service checks data
    // 3. Database service saves user
    // 4. Email service sends confirmation
    // 5. User receives success message
});

// End-to-End Testing Example
// Test complete user journey
test('complete shopping flow', () => {
    // 1. User visits website
    // 2. User browses products
    // 3. User adds items to cart
    // 4. User proceeds to checkout
    // 5. User enters payment details
    // 6. User completes purchase
    // 7. User receives confirmation email
});

Swipe to see more code

// Unit Testing Example
function calculateTotal(items) {
    return items.reduce((sum, item) => sum + item.price, 0);
}

// Unit test
test('calculateTotal should return correct sum', () => {
    const items = [
        { price: 10 },
        { price: 20 },
        { price: 30 }
    ];
    expect(calculateTotal(items)).toBe(60);
});

// Integration Testing Example
// Test how components work together
test('user registration flow', () => {
    // 1. User submits form
    // 2. Validation service checks data
    // 3. Database service saves user
    // 4. Email service sends confirmation
    // 5. User receives success message
});

// End-to-End Testing Example
// Test complete user journey
test('complete shopping flow', () => {
    // 1. User visits website
    // 2. User browses products
    // 3. User adds items to cart
    // 4. User proceeds to checkout
    // 5. User enters payment details
    // 6. User completes purchase
    // 7. User receives confirmation email
});

Scroll

🎯 Practice Exercise

Test your understanding of this topic:

I understand the basic concepts covered in this topicI can apply the concepts in practical scenariosI'm ready to move to the next topic

Software Testing Fundamentals

Select Topics Overview

Introduction to Software Testing

Software Development Life Cycle (SDLC)

Testing Life Cycle (STLC)

Types of Testing

Testing Levels & Phases

Introduction to Software Testing

Software Development Life Cycle (SDLC)

Testing Life Cycle (STLC)

Types of Testing

Testing Levels & Phases

Introduction to Software Testing

What is Software Testing?

Why is Software Testing Important?

Software Testing Principles

Testing vs Debugging

🎯 Practice Exercise

Software Development Life Cycle (SDLC)

SDLC Phases

SDLC Models

Testing in Different SDLC Models

🎯 Practice Exercise

Testing Life Cycle (STLC)

STLC Phases

Test Planning Activities

Test Analysis and Design

🎯 Practice Exercise

Types of Testing

Functional Testing

Non-Functional Testing

Testing Types by Approach

🎯 Practice Exercise

Testing Levels & Phases

Testing Pyramid Levels

Unit Testing

Integration Testing

Testing Level Examples

🎯 Practice Exercise

Module 2: Manual Testing Techniques

Ready for the Next Module?