1/25
Prerequisite for Testing Activities
A condition or requirement that must be available and satisfy minimal requirements before starting test execution (e.g., environment, browser, initialized database).
5 Core Sequential Test Activities
1) Identify test conditions, 2) Design test cases, 3) Build test cases, 4) Execute test cases, 5) Compare test outcomes.
Sequential Nature of Test Development
Activities must occur in order for a test case: Identify (what) -> Design (how) -> Build -> Execute -> Compare.
Formality in Testing Activities
Activities can be done formally (with documentation at each step) or informally (when the tester sits down to test).
Identify Test Conditions (Activity 1)
Determines 'what' can be tested and prioritizes them based on risk and importance.
Test Condition (Definition)
An item or event of a system that could be verified by a test.
Techniques to Derive Test Conditions
Rigorous and systematic testing techniques such as Equivalence Partitioning, Boundary Value Analysis, and Cause-Effect Graphing.
When to Identify Test Conditions
Best performed in parallel with associated development activities (on the left-hand side of the V-model).
Documentation of Test Conditions
Can be documented as brief sentences, table entries, or flow graphs (diagrams).
Design Test Cases (Activity 2)
Determines 'how' the 'what' will be tested by producing test inputs, expected outcomes, and prerequisites.
Test Case (Definition)
A set of tests performed in a sequence related to a specific test objective.
Components of a Test Case Design
1) Specific input values, 2) Expected outcomes, 3) Execution prerequisites (e.g., environment setup).
What Expected Outcomes Include
Outputs/records created, data that must NOT be changed or updated, and items that must be deleted.
Cross-Referencing / Traceability Tags
Tags (e.g., VB10 for 10th Valid Boundary, V8 for 8th Valid Partition) used to link test conditions directly to test cases.
Goal of Test Case Design Skill
Ensuring test cases find a high proportion of defects while remaining well-designed to avoid excessive costs.
Build Test Cases (Activity 3)
Implementing test cases by preparing test scripts, test inputs, test data, expected outcomes, and initializing preconditions.
Test Script
Data and/or instructions with formal syntax used by an execution tool (automated), or a manual test procedure followed by a tester.
Preconditions in Test Building
Ensuring databases are initialized with expected data, and required hardware/software (printers, network) is available.
Expected Outcomes: Automated vs. Manual
Automated tools require everything spelled out in strict detail and rigor, whereas manual testing may rely on notes in procedures.
Software Test Document (STD)
Formal documentation used to record test specifications, scripts, and implementation details.
Execute Test Cases (Activity 4)
Running the software under test either manually (following procedures and logging observations) or automated (starting test tools).
Compare Test Outcomes (Activity 5)
Investigating actual outcomes against expected outcomes to check if the software worked correctly.
Types of Outcome Comparison
1) Real-time comparison during execution (e.g., screen messages), 2) Post-execution comparison (e.g., database changes).
Why Discrepancy ≠ Software Bug (Oversimplification)
A discrepancy can also be caused by running tests in the wrong sequence, incorrect expected outcomes, misconfigured test environments, or incorrectly specified tests.
Comparing vs. Verifying
A tool can only compare (flag differences between two sets of data), but cannot verify (confirm whether the result is actually correct); verification requires a human tester.