Discussion Topics:

• How do the three boundary value analysis techniques (standard, robust, worst-case) differ in approach and application?
• What are the trade-offs between robust testing and worst-case testing in terms of effort and coverage?
• Discuss a scenario where boundary value checks could prevent a critical software failure.
• How can boundary value analysis be combined with other testing techniques for better results?

Lesson Summary: This week delves deeper into boundary value analysis, covering standard BVA, robust testing, and worst-case testing. Students learn to apply these techniques to identify boundary-related defects. Teaching methods include classroom discussions, lecture videos, and open discussions, with lab performance assessments targeting CLO2 (applying testing knowledge) and CLO3 (problem-solving through testing).

Instructions for Lab Report 2:

Lab Report 2: Boundary Value Analysis for Input Validation

Objective: Apply Boundary Value Analysis (BVA) to test input boundaries and identify defects.

Learning Outcome: Students will be able to apply BVA to create test cases that cover boundary conditions, analyzing their effectiveness in detecting defects (CLO1, CLO2, PLO1, Cognitive Domain: Analyze - C4).

Tools Required: Any C Compiler.

Instructions:

1. Choose a program accepting numerical inputs within a range (e.g., a function for ages 18–60).
2. Apply BVA to identify boundary values (min, min+1, max, max-1, etc.).
3. Create a test suite with at least 8 test cases, including nominal, boundary, and invalid inputs.
4. Execute the test cases and log results in a table.
5. Analyze whether the program handles boundary conditions correctly and suggest improvements.

Deliverables:

• A lab report with test cases, execution logs, and an analysis of boundary-related defects.
• Include a table summarizing test results.

Assessment: Lab Performance (CLO1, CLO2, PLO1).