Software Testing Reviewer Flashcards

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/79

flashcard set

Earn XP

Description and Tags

Comprehensive 80-card review set covering key software testing concepts, methodologies, levels, quality control distinctions, principles, and STLC phases.

Last updated 4:36 AM on 10/3/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

80 Terms

1
New cards

What is Software Testing?

The process of checking whether software works as expected and meets its requirements.

2
New cards

What does Application Under Test (AUT) refer to?

The software or application currently being tested.

3
New cards

What is defined as a Defect in software testing?

A problem or flaw in software that can cause it not to work as expected.

4
New cards

What are the key benefits of software testing?

Finding bugs early, reducing fixing costs, improving security, software quality, performance, customer satisfaction, and reducing risks.

5
New cards

What is the core rule regarding early testing?

Test early = Find problems early = Cheaper to fix.

6
New cards

How does software testing achieve cost-effectiveness?

By finding bugs early, which costs less than fixing them later.

7
New cards

How does testing address security?

It helps find security weaknesses and vulnerabilities to protect the system and user information.

8
New cards

How does software testing impact product quality?

It ensures the software meets its requirements and provides a quality product.

9
New cards

How does software testing affect customer satisfaction?

It improves the user's experience by making the software work properly.

10
New cards

What is Verification in software testing?

Checking if the software follows the correct design and specifications.

11
New cards

What is the main question asked during Verification?

Are we building the product right?

12
New cards

What four areas does Verification focus on?

Design, specifications, business requirements, and development methods.

13
New cards

What is Validation in software testing?

Checking if the software satisfies user requirements.

14
New cards

What is the main question asked during Validation?

Are we building the right product?

15
New cards

What does Validation focus on?

User requirements and the actual needs of the user.

16
New cards

What is the memory trick to remember Verification vs Validation?

Verification connects to specifications, while Validation connects to user needs.

17
New cards

What is an Error in software testing?

An actual mistake made during software development or coding.

18
New cards

What is a Fault or Bug?

A problem that happens because of an error and can cause the system to fail.

19
New cards

What is a Failure in software testing?

When the system cannot perform the required task.

20
New cards

What is the sequence of software problem escalation?

Error -> Fault/Bug -> Failure.

21
New cards

In the sequence example, what represents the Error?

A programmer writing the wrong calculation.

22
New cards

In the sequence example, what represents the Fault/Bug?

The incorrect code remaining in the program.

23
New cards

In the sequence example, what represents the Failure?

The system giving the wrong result.

24
New cards

What is Manual Testing?

Testing performed without automated testing tools, where a human tester creates test cases, runs tests, checks results, and reports results.

25
New cards

What are the main disadvantages of Manual Testing?

It takes more time and uses more resources.

26
New cards

What is Automated Testing?

Testing performed using automated testing tools.

27
New cards

What types of testing are automated tools particularly useful for?

Load testing, stress testing, and regression testing.

28
New cards

What is the simple comparison between Manual and Automated testing?

Manual relies on a person, while Automated relies on a tool.

29
New cards

What are the two major approaches to testing?

Functional Testing and Non-Functional Testing.

30
New cards

What is Functional Testing?

Testing whether each function of the software works according to the requirements.

31
New cards

What is the simple question associated with Functional Testing?

What does the system do?

32
New cards

What main aspects does Functional Testing focus on?

Functions, features, inputs, outputs, and requirements.

33
New cards

Under which broader testing type does Functional Testing fall?

Black-Box Testing.

34
New cards

What is Non-Functional Testing?

Testing how well the system performs.

35
New cards

What is the simple question associated with Non-Functional Testing?

How well does the system work?

36
New cards

What specific characteristics can Non-Functional Testing test?

Performance, load, stress, scalability, security, and compatibility.

37
New cards

What is the memory trick for Functional vs Non-Functional testing?

Functional = WHAT; Non-functional = HOW WELL.

38
New cards

What is Black-Box Testing?

Testing the functionality of software without looking at its internal code or structure.

39
New cards

What is another name for Black-Box Testing?

Behavioral Testing.

40
New cards

What is the main focus of Black-Box Testing?

Input -> System -> Output.

41
New cards

What is Equivalence Class testing?

Dividing inputs into groups or classes that should behave similarly and testing representative values.

42
New cards

What is Boundary Value Testing?

Testing values at the edges or boundaries (lowest and highest limits) of an input range.

43
New cards

Why are boundary values tested in software testing?

Because errors commonly happen at boundaries.

44
New cards

What is Cause-Effect Graphing?

Testing combinations of inputs (causes) and their expected outputs (effects).

45
New cards

What is Pair-Wise Testing?

Testing combinations of two parameters at a time.

46
New cards

What is State-Based Testing?

Testing a system based on its different states and how inputs change those states.

47
New cards

What is White-Box Testing?

Testing the internal code, structure, and implementation of the program.

48
New cards

What is another name for White-Box Testing?

Structural Testing.

49
New cards

Who usually performs White-Box Testing?

Programmers / developers.

50
New cards

What is Control-Flow Testing?

Testing the flow of the program by covering statements and testing branch conditions as True and False.

51
New cards

What is Data-Flow Testing?

Testing how variables are declared, defined, used, and changed through the program.

52
New cards

What is Exhaustive Testing?

Testing every possible input and output value.

53
New cards

Why is Exhaustive Testing practically impossible in real-world systems?

Because there can be too many possible inputs (billions of values), taking too much time and money.

54
New cards

What are the four main levels of software testing?

Unit Testing, Integration Testing, System Testing, and Acceptance Testing.

55
New cards

What is Unit Testing?

Testing individual units or parts of a program.

56
New cards

Who usually performs Unit Testing and what testing approach is commonly used?

Programmers usually perform it using the white-box approach.

57
New cards

What is Integration Testing?

Testing whether individual software units work correctly when combined.

58
New cards

What is System Testing?

Testing the complete software as a whole.

59
New cards

What testing types can be included in System Testing?

Functionality testing, performance testing, security testing, and portability testing.

60
New cards

What is Acceptance Testing?

Testing performed when the software is ready to be handed to the customer/user to check if it is acceptable.

61
New cards

What is Alpha Testing?

Testing performed internally by the development team, using the system as if in a real environment.

62
New cards

What is Beta Testing?

Testing performed by users after internal testing, in their own/production environment.

63
New cards

What is Regression Testing?

Testing software again after changes, updates, or new features to ensure existing functions were not negatively affected.

64
New cards

What is Performance Testing?

Testing how efficiently and quickly the software performs its required tasks.

65
New cards

What is Load Testing?

Testing the system under a particular amount of users or data to see if it can handle the expected load.

66
New cards

What is Stress Testing?

Putting the system under high load to see how it behaves when heavily overloaded.

67
New cards

What is Software Quality Assurance (QA)?

Monitoring the software development process to make sure proper standards and methods are followed.

68
New cards

What is Software Quality Control (QC)?

A system used to maintain the quality of the software product.

69
New cards

What is a Software Audit?

An independent review of the organization's software development procedures and processes to check compliance with standards, rules, and regulations.

70
New cards

What does the principle 'Testing Shows Presence of Defects' state?

Testing can show that defects exist, but cannot prove that there are no defects.

71
New cards

What should testers consider since Exhaustive Testing is impossible?

Risk, priority, time, and cost.

72
New cards

What does the Early Testing principle state?

Testing should begin early in the SDLC because finding bugs early makes them cheaper to fix.

73
New cards

What is Defect Clustering and what principle is it related to?

Most defects are usually concentrated in a small number of modules; it relates to the Pareto Principle / 80-20 Rule.

74
New cards

What is the Pesticide Paradox in software testing?

If the same test cases are repeatedly used, they may eventually stop finding new defects.

75
New cards

How can testers address the Pesticide Paradox?

By reviewing test cases, updating test cases, and adding new test cases.

76
New cards

What does the principle 'Testing is Context Dependent' mean?

Testing depends on the type and purpose of the software (e.g., online banking vs e-commerce).

77
New cards

What is the Absence-of-Error Fallacy?

Having very few bugs does not automatically mean the software is useful if it does not meet business or user needs.

78
New cards

What is the Software Testing Life Cycle (STLC)?

A sequence of activities performed during software testing to ensure software quality, including verification and validation.

79
New cards

What is the difference between Entry Criteria and Exit Criteria?

Entry Criteria are conditions that must be completed BEFORE a testing phase begins; Exit Criteria must be completed BEFORE leaving a phase.

80
New cards

What is a Requirement Traceability Matrix (RTM)?

A document used to connect requirements with testing to track requirements and their tests.