Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

CSCC 33.1 > Introduction to Software Testing > Flashcards

Introduction to Software Testing Flashcards

(65 cards)

Start Studying
1
Q

It is the process of executing the program with the intent of finding faults

A

Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

It is the fourth phase of the software development life cycle (SDLC)

A

Software Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Is testing the same as debugging?

A

No

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

It removes known errors

A

Debugging

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

It finds hidden errors

A

Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Testing starts during ___________________ and goes until the last ____________ phase

A

Requirements Analysis ; Maintenance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

In the early stages of development, we do static testing. This means we review the _____________ to check if it meets user requirements.

A

Software Requirements Specification (SRS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

One of the five distinct levels of testing which is defined as the successful correction of a failure.

A

Debug

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

One of the five distinct levels of testing which is the process of showing that major features work with typical input.

A

Demonstrate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

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.

A

Verify

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

One of the five distinct levels of testing which is the process of finding many faults in requirements, design, and AUT.

A

Validate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

One of the five distinct levels of testing which is to avoid errors in development of requirements, design, and AUT.

A

Prevent

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

This type of testing checks if the system works correctly with valid inputs

A

Positive Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

This type of testing tries to break the system using invalid or extreme inputs.

A

Negative Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

A good tester wants the system to fail to reveal hidden defects.

A

Destructive Mentality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

The formula for Software Testing

A

Software Testing = Software Verification + Software Validation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

It ensures development artifacts (requirements, design, code) meet their intended purpose.

A

Verification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

It ensures the final product meets user requirements,

A

Validation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

The stage of incremental testing approach where you learn the application

A

Exploration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

The stage of incremental testing approach where you run a simple test case

A

Baseline Test

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

The stage of incremental testing approach where you check performance when output is unpredictable.

A

Trends Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

The stage of incremental testing approach where you identify data categories and create tests.

A

Inventory

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

The stage of incremental testing approach where test different input combinations

A

Inventory Combinations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

The stage of incremental testing approach where you test extreme input values

A

Push the Boundaries

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
The stage of incremental testing approach where you use invalid or unexpected data to see system response
Devious Data
26
The stage of incremental testing approach where you try to break the system.
Stress the Environment
27
The first stage of Incremental Testing Approach
Exploration
28
The second stage of Incremental Testing Approach
Baseline Test
29
The third stage of Incremental Testing Approach
Trend Analysis
30
The fourth stage of Incremental Testing Approach
Inventory
31
The fifth stage of Incremental Testing Approach
Inventory Combinations
32
The sixth stage of Incremental Testing Approach
Push the Boundaries
33
The seventh stage of Incremental Testing Approach
Devious Data
34
The last stage of Incremental Testing Approach
Stress the Environment
35
These are human mistakes made during development
Errors
36
Where can errors grow during the project?
They pass from requirements to coding
37
It is a missing or incorrect statement in the code caused by an error
Fault (Defect)
38
It occurs when a fault executes and the system does not behave as expected
Failure
39
It is shown by wrong outputs, crashes, or unmet constraints
Failure
40
It is a sign or symptom of failure
Incident
41
It alerts users to a problem but may not require a fix.
Incident
42
It is the act of running the software with specific inputs
Test
43
It aims to either find failures or show that the software works correctly.
Test
44
It is a defined set of inputs, steps, and expected outputs
Test Case
45
It provides structured validations of software functionality, making them a core part of quality assurance.
Test Case
46
It helps determine if the program passes or fails.
Test Case
47
Conditions that must be met before running the test.
Preconditions
48
Data used during testing.
Actual Input
49
Expected state after execution.
Postconditions
50
Observed results during testing.
Outputs
51
Detailed, step-by-step instructions to run test cases.
Text Script
52
A collection of test cases or scripts grouped together for testing a specific aspect of a product
Test Suite
53
Used for validating bug fixes or finding new defects in a logical or physical part of the system.
Test Suite
54
All testing documents (specifications, scripts, cases, data)
Test Ware
55
A method to predict expected outcomes.
Test Oracle
56
A chronological record of test execution details.
Test Log
57
A document summarizing the testing process and results/
Test Report
58
This is the Testing life Cycle Phase where bugs are introduced during requirements, design, and coding
Development Phase
59
This is the Testing life Cycle Phase where faults from early phases can propagate into later stages.
Development Phase
60
This is the Testing life Cycle Phase where bugs are identified through verification and validation.
Testing Phase
61
This is the Testing life Cycle Phase where testing ensures that defects are detected before release.
Testing Phase
62
This is the Testing life Cycle Phase where bugs are fixed and removed from the system.
Bug Resolution Phase
63
This is the Testing life Cycle Phase where fixes can introduce new faults if not handled correctly.
Bug Resolution Phase
64
An approach where you stop when you run out of allocated resources (times, budget, or test cases).
Pessimistic Approach
65
An approach where you stop when the system meets the required reliability or when further testing cost outweighs its benefit.
Optimistic Approach

CSCC 33.1 (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions