Save
...
13.0 Systematic approach to problem solving
13.4 Testing
13.4.1 Types of testing
Save
Share
Learn
Content
Leaderboard
Share
Learn
Cards (23)
Regression testing is performed only once in the software development lifecycle.
False
Testing ensures the software is functional, accurate, and
reliable
What are the key purposes of testing in software development?
Ensuring reliability and quality
Match the type of testing with its purpose:
Unit Testing ↔️ Checks individual components
Integration Testing ↔️ Verifies interaction between components
System Testing ↔️ Evaluates the entire system's functionality
Acceptance Testing ↔️ Determines if the system meets user needs
Regression Testing ↔️ Ensures new code changes don't introduce bugs
Order the steps involved in black-box testing techniques
1️⃣ Equivalence Partitioning
2️⃣ Boundary Value Analysis
3️⃣ Decision Table Testing
White-box testing requires knowledge of the software's
internal code
structure.
Testing in software development is crucial for ensuring software works correctly and finding errors or
defects
Testing verifies that software functions as intended according to its
specifications
.
What does testing improve in software?
Quality and performance
Regression testing ensures that new code changes do not introduce new
bugs
What is the focus of black-box testing?
Inputs and outputs
Match the black-box testing technique with its explanation.
Equivalence Partitioning ↔️ Tests one value from each class
Boundary Value Analysis ↔️ Tests values at input boundaries
Decision Table Testing ↔️ Ensures every rule is tested
Boundary value analysis focuses on testing values at the edge of equivalence
partitions
What does decision table testing ensure in complex conditions?
Every rule is tested
What does white-box testing examine in software?
Code structure and logic
Match the white-box testing technique with its explanation.
Statement Coverage ↔️ Tests every statement once
Branch Coverage ↔️ Tests all possible branches
Path Coverage ↔️ Tests all execution paths
Statement coverage tests every statement in the
code
at least once.
What does branch coverage ensure in if-else blocks?
All branches are tested
Regression testing is performed after each code
change
What is the primary goal of regression testing?
Ensure no new bugs
Regression testing is performed after each
change
Who typically performs acceptance testing?
End-users or clients
Grey-box testing uses partial knowledge of the
code
.
See similar decks
13.4.1 Types of testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
151 cards
13.4.1 Types of testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
52 cards
13.4.1 Types of testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
37 cards
13.4.1 Types of testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
37 cards
13.4.1 Types of testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
37 cards
13.4.1 Types of testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
80 cards
13.4 Testing
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving
54 cards
3.4 Testing
AQA A-Level Computer Science > 3.0 Systematic approach to problem solving
29 cards
13.2.1 Creating algorithms
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.2 Design
135 cards
13.3.1 Writing code
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.3 Implementation
81 cards
13.4.2 Test plans and test cases
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.4 Testing
31 cards
13.2 Design
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving
200 cards
13.0 Systematic approach to problem solving
AQA A-Level Computer Science
512 cards
13.5 Evaluation
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving
69 cards
13.3 Implementation
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving
131 cards
13.1 Problem definition
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving
58 cards
13.1.1 Identifying requirements
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.1 Problem definition
34 cards
13.2.2 Data modeling
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.2 Design
65 cards
13.5.2 Identifying improvements
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.5 Evaluation
43 cards
13.3.2 Version control
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.3 Implementation
50 cards
13.1.2 Constraints and assumptions
AQA A-Level Computer Science > 13.0 Systematic approach to problem solving > 13.1 Problem definition
24 cards