Introduction to Software Testing Flashcards
It is the process of executing the program with the intent of finding faults
Testing
It is the fourth phase of the software development life cycle (SDLC)
Software Testing
Is testing the same as debugging?
No
It removes known errors
Debugging
It finds hidden errors
Testing
Testing starts during ___________________ and goes until the last ____________ phase
Requirements Analysis ; Maintenance
In the early stages of development, we do static testing. This means we review the _____________ to check if it meets user requirements.
Software Requirements Specification (SRS)
One of the five distinct levels of testing which is defined as the successful correction of a failure.
Debug
One of the five distinct levels of testing which is the process of showing that major features work with typical input.
Demonstrate
One of the five distinct levels of testing which is the process of finding as many faults in the application under test (AUT) as possible.
Verify
One of the five distinct levels of testing which is the process of finding many faults in requirements, design, and AUT.
Validate
One of the five distinct levels of testing which is to avoid errors in development of requirements, design, and AUT.
Prevent
This type of testing checks if the system works correctly with valid inputs
Positive Testing
This type of testing tries to break the system using invalid or extreme inputs.
Negative Testing
A good tester wants the system to fail to reveal hidden defects.
Destructive Mentality
The formula for Software Testing
Software Testing = Software Verification + Software Validation
It ensures development artifacts (requirements, design, code) meet their intended purpose.
Verification
It ensures the final product meets user requirements,
Validation
The stage of incremental testing approach where you learn the application
Exploration
The stage of incremental testing approach where you run a simple test case
Baseline Test
The stage of incremental testing approach where you check performance when output is unpredictable.
Trends Analysis
The stage of incremental testing approach where you identify data categories and create tests.
Inventory
The stage of incremental testing approach where test different input combinations
Inventory Combinations
The stage of incremental testing approach where you test extreme input values
Push the Boundaries
The stage of incremental testing approach where you use invalid or unexpected data to see system response
Devious Data
The stage of incremental testing approach where you try to break the system.
Stress the Environment
The first stage of Incremental Testing Approach
Exploration
The second stage of Incremental Testing Approach
Baseline Test
The third stage of Incremental Testing Approach
Trend Analysis
The fourth stage of Incremental Testing Approach
Inventory
The fifth stage of Incremental Testing Approach
Inventory Combinations
The sixth stage of Incremental Testing Approach
Push the Boundaries
The seventh stage of Incremental Testing Approach
Devious Data
The last stage of Incremental Testing Approach
Stress the Environment
These are human mistakes made during development
Errors
Where can errors grow during the project?
They pass from requirements to coding
It is a missing or incorrect statement in the code caused by an error
Fault (Defect)
It occurs when a fault executes and the system does not behave as expected
Failure
It is shown by wrong outputs, crashes, or unmet constraints
Failure
It is a sign or symptom of failure
Incident
It alerts users to a problem but may not require a fix.
Incident
It is the act of running the software with specific inputs
Test
It aims to either find failures or show that the software works correctly.
Test
It is a defined set of inputs, steps, and expected outputs
Test Case
It provides structured validations of software functionality, making them a core part of quality assurance.
Test Case
It helps determine if the program passes or fails.
Test Case
Conditions that must be met before running the test.
Preconditions
Data used during testing.
Actual Input
Expected state after execution.
Postconditions
Observed results during testing.
Outputs
Detailed, step-by-step instructions to run test cases.
Text Script
A collection of test cases or scripts grouped together for testing a specific aspect of a product
Test Suite
Used for validating bug fixes or finding new defects in a logical or physical part of the system.
Test Suite
All testing documents (specifications, scripts, cases, data)
Test Ware
A method to predict expected outcomes.
Test Oracle
A chronological record of test execution details.
Test Log
A document summarizing the testing process and results/
Test Report
This is the Testing life Cycle Phase where bugs are introduced during requirements, design, and coding
Development Phase
This is the Testing life Cycle Phase where faults from early phases can propagate into later stages.
Development Phase
This is the Testing life Cycle Phase where bugs are identified through verification and validation.
Testing Phase
This is the Testing life Cycle Phase where testing ensures that defects are detected before release.
Testing Phase
This is the Testing life Cycle Phase where bugs are fixed and removed from the system.
Bug Resolution Phase
This is the Testing life Cycle Phase where fixes can introduce new faults if not handled correctly.
Bug Resolution Phase
An approach where you stop when you run out of allocated resources (times, budget, or test cases).
Pessimistic Approach
An approach where you stop when the system meets the required reliability or when further testing cost outweighs its benefit.
Optimistic Approach
