Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Quality Assurance > Reviews and Testing > Flashcards

Reviews and Testing Flashcards

1
Q

An evaluation of a life-cycle work product(s) or project status to determine if there are any deviations from planned results and to recommend improvement.

A

Review

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

Any condition that deviates from expectations based on requirements specifications, design documents, standards, plans, and so on, or from someone’s experiences.

A

Anomaly (defect)

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

A formal evaluation of a project-level plan or project progress relative to that plan by a designated review team.

A

Management review

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

Milestones might be linked to customer involvement and even contract payments such as in the defense world of conducting PDRs and CDRs.

What does PDR stand for?

A

Preliminary Design Review

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

Milestones might be linked to customer involvement and even contract payments such as in the defense world of conducting PDRs and CDRs.

What does CDR stand for?

A

Critical Design Review

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

An informal verification technique in which the life-cycle work product is examined by the author and one other person.

A

Buddy check

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

A formal team evaluation of a life-cycle work product to:

  • Identify any discrepancies from specifications and standards.
  • Determine its suitability for use.
  • Provide recommendations after the examination of various alternatives.
A

Technical review

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

Technical reviews are typically used for the classic design reviews such as PDRs, CDRs, and TRRs.

What does TRR stand for?

A

Test Readiness Review

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

A formal verification technique in which life-cycle work products are examined in detail by a group of peers for the explicit purpose of detecting and identifying defects.

A

Inspection

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

A quality control function in that it is used to verify the functionality and performance of life-cycle work products or product components as they move through the product life cycle.

A

Testing

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

___ testing is a process of testing the individual components, subsystems, hardware components such as programmable logic arrays, and software components such as subprograms, subroutines, or procedures.

A

Unit

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

The objective of ___ testing is to test component interfaces and confirm that the components meet the interface requirements and that the components can indeed be assembled.

A

integration

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

___ testing is the first time at which the entire system can be tested against the system requirements specifications.

A

Systems

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

The purpose of ___ testing is to confirm that a system is ready for operational use and that the confidence built up in systems testing is justified.

A

acceptance

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

___ testing is the execution of a series of tests to check that modifications to parts of an existing system will not negatively affect other working components or sybsystems.

A

Regression

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

The process of finding areas of a program not exercised by a set of test cases, creating additional test cases to increase coverage, and determining a quantitative measure of code coverage that serves an indirect measure of quality.

A

Test coverage analysis

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

___ coverage measures whether each executable statement is encountered.

A

Statement

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

___ coverage measures whether Boolean expressions tested in control structures are evaluated to both true and false.

A

Decision

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

___ coverage measures the true or false outcome of each Boolean subexpression.

A

Condition

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

___ coverage measures whether every possible combination of Boolean subexpression occurs.

A

Multiple condition

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

___ coverage measures whether each of the possible paths in each function has been followed.

A

Path

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

Test case design technique. Tests that exercise all decision point outcomes at least once, and ensure that all statements or entry points are executed at least once.

A

Logic coverage

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

Test case design technique. Defines condition or error classes to help reduce the number of finite tests. Assumes that a test of a representative value within a class also tests all values or conditions within that class.

A

Equivalence partitioning

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

Test case design technique. Tests each edge condition of an equivalence class; also considers output equivalence classes as well as input classes.

A

Boundary value analysis

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

Test case design technique. Produces Boolean graphical representations of potential test case results to aid in selecting efficient and complete test cases.

A

Cause-effect graphing

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

Test case design technique. Produces test cases based on intuitive and expert knowledge of test team members to define potential software errors to facilitate efficient test case design.

A

Error guessing

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

An evaluation of a life-cycle work product(s) or project status to determine if there are any deviations from planned results and to recommend improvement.

A

Review

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

Human-based testing.

A

Peer review

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

Any condition that deviates from expectations based on requirements specifications, design documents, standards, plans, and so on, or from someone’s experiences.

A

Anomaly (defect)

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

A formal evaluation of a project-level plan or project progress relative to that plan by a designated review team.

A

Management review

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

An informal verification technique in which the life-cycle work product is examined by the author and one other person.

A

Buddy check

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

The life-cycle work product is circulated to each reviewer who reviews it and either attaches comments, questions, and recommendations directly on the life-cycle work product or places them into a separate document.

A

Circulation review

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

A formal team evaluation of a life-cycle work product to:

  • Identify any discrepancies from specifications and standards.
  • Determine its suitability for use.
  • Provide recommendations after the examination of various alternatives.
A

Technical review

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

A formal verification technique in which life-cycle work products are examined in detail by a group of peers for the explicit purpose of detecting and identifying defects.

A

Inspections

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

Designed to be a less formal verification technique in which life-cycle work products are examined by a group of peers for the purpose of finding defects, omissions, and contradictions. Normally led by the author or the producer of the material being reviewed.

A

Walkthrough

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

___ walkthroughs are more closely aligned with inspections than the informal walkthrough.

A

Structured

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

Step in the inspection process. The inspection process is only entered when a specified set of entry criteria have been met.

A

Entry

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

Step in the inspection process. The moderator is responsible for leading the inspection planning effort.

A

Planning

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

Step in the inspection process. The moderator conducts a “kickoff” meeting prior to checking.

A

Kickoff

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

Step in the inspection process. Each inspection team member inspects the life-cycle work product and logs possible major and minor defects.

A

Checking

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

Step in the inspection process. This is the part of the inspection where the reviewers meet face to face to log and consolidate the defects found during their individual checking period.

A

Logging

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

Step in the inspection process. The analysis sub-process of the inspection process is a phase I created by separating it from the logging phase.

A

Analyzing

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

Step in the inspection process. Immediately, if possible, or shortly after the logging and analysis meeting, time may be allotted to brainstorming the defect causes and process improvements to prevent these causes.

A

Process Improvement Brainstorming.

44
Q

Step in the inspection process. Some written action, including corrective action, must be carried out by the author or an editor.

A

Edit

45
Q

Step in the inspection process. The moderator determines whether the formal exit criteria have been met before signing off on completion of the inspection process.

A

Exit

46
Q

A quality control function in that it is used to verify the functionality and performance of life-cycle work products or product components as they move through the products life cycle.

A

Testing

47
Q

___ testing is a process of testing the individual components, subsystems, hardware components such as programmable logic arrays, and software components such as subprograms, subroutines, or procedures.

A

Unit

48
Q

The objective of ___ testing is to test component interfaces and confirm that the components meet the interface requirements and that the components can indeed be assembled.

A

integration

49
Q

___ testing is the first time at which the entire system can be tested against the systems requirements specifications.

A

Systems

50
Q

The purpose of ___ testing is to confirm that a system is ready for operational use and that the confidence built up in systems testing is justified.

A

acceptance

51
Q

___ testing is the execution of a series of tests to check that modifications to parts of an existing system will not negatively affect other working components or subsystems.

A

Regression

52
Q

___ coverage measures whether each executable statement is encountered.

A

Statement

53
Q

The process of finding areas of a program not exercised by a set of test cases, creating additional test cases to increase coverage, and determining a quantitative measure of code coverage that serves an indirect measure of quality.

A

Test coverage analysis

54
Q

___ coverage measures whether Boolean expressions tested in control structures are evaluated to both true and false.

A

Decision

55
Q

___ coverage measures the true or false outcome of each Boolean subexpression.

A

Condition

56
Q

___ coverage measures whether every possible combination of Boolean sub-expression occurs.

A

Multiple condition

57
Q

___ coverage measures whether each of the possible paths in each function has been followed.

A

path

58
Q

___ testing involves the testing of individual hardware or software units or groups of related items prior to integration of those items.

A

Unit

59
Q

The master ___ contains general, high-level information regarding unit testing, integration testing, and hardware/software system testing.

A

software test plan

60
Q

The ___ is intended to guide the testing and verification of all functions within each coded program module and subsystem before it is integrated and system tested.

A

unit test specifications/procedure

61
Q

What is not a part of a test strategy?

a) QA deliverables
b) Scope of testing
c) Test scenarios
d) References

A

c) Test scenarios

62
Q

(T/F) A test plan is created for each feature.

A

True

63
Q

(T/F) Acceptance criteria is written for each feature.

A

False

64
Q

The definition of done specifies when ___.

a) automation testing has been completed
b) a developer says a feature is complete
c) a piece of functionality has completed development
d) testing is complete

A

d) testing is complete

65
Q

Which technique is used to test the entire logic or source code of a program?

a) Unit
b) Black-box
c) Smoke
d) White-box

A

d) White-box

66
Q

Which technique is used to test a program according to specifications?

a) Unit
b) Black-box
c) Smoke
d) White-box

A

b) Black-box

67
Q

___ testing focuses on the interaction between application components.

A

Integration

68
Q

Integration tests are ___ box tests.

A

gray

69
Q

___ testing benchmarks how a system performs under load.

A

Performance

70
Q

Performance testing is a type of ___ box testing.

A

black

71
Q

___ testing checks the application’s ability to perform under user loads.

A

Load

72
Q

___ testing checks how an application handles load over time.

A

Endurance

73
Q

___ testing involves testing an application under extreme workloads. It is used for testing scalability.

A

Stress

74
Q

___ testing exposes problems in the application that can cause unexpected behavior or crashes.

A

Security

75
Q

Used to insert database statements into text fields and expose application information.

A

SQL injection

76
Q

An attack where hackers try to take down an application’s servers or network.

A

DoS

77
Q

DoS is an attack where hackers try to take down an application’s servers or network.

What does DoS stand for?

A

Denial of Service

78
Q

___ in dependencies can cause massive security problems.

A

Vulnerabilities

79
Q

___ box testing examines the interaction between the outside and inside of a box.

A

gray

80
Q

(T/F) Manual testing should be performed based on scenarios in a test plan.

A

True

81
Q

(T/F) All scenarios from a test plan should be written as UI automation tests.

A

False

82
Q

Integration testing focuses on the ___ between components.

a) development
b) interaction
c) edge cases
d) test scenarios

A

b) interaction

83
Q

What type of testing is done to make sure that the software can handle the expected load over a long period of time?

A

endurance testing

84
Q

(T/F) Security testing is performed to reveal flaws or vulnerabilities that can be exposed in an application by users.

A

True

85
Q

Which testing process validates a program’s specifications?

A

Functional

86
Q

___ testing is the process of finding discrepancies between a program and a set of external specifications.

A

Functional

87
Q

Which testing process determines how well a program behaves during failure and/or data loss?

A

Recovery

88
Q

___ testing is used to determine how well a program recovers in the event of failure or data loss.

A

Recovery

89
Q

Which testing process includes collaboration with the customer in continuous testing across multiple iterations of a project?

a) Recovery
b) Functional
c) Stress
d) Agile

A

d) Agile

90
Q

___ testing includes multiple iterations where collaboration on development and testing with the customer is key.

A

Agile

91
Q

___ testing is used to determine how well a program recovers in the event of failure or data loss.

A

Recovery

92
Q

___ testing is the process of finding discrepancies between a program and a set of external specifications.

A

Functional

93
Q

___ testing is the process of testing a heavy load on a program or network.

A

Stress

94
Q

What is a challenge in verifying the functionality of mobile applications on a device?

a) Diversity
b) Screen resolution
c) Testing tools
d) Battery power

A

a) Diversity

95
Q

___ testing is the process of testing individual components that make up a program.

A

Module (unit)

96
Q

Which unit test combines the current module with the previously tested module?

a) Stress
b) Non-incremental
c) Reductive
d) Incremental

A

d) Incremental

97
Q

In the ___ testing process, modules are combined with the previously tested module.

A

incremental

98
Q

___ testing/debugging is the process of removing components until an issue in the code is located.

A

Reductive

99
Q

In ___ testing, modules are individually tested.

A

non-incremental

100
Q

___ testing is the process of testing a heavy load on an application or network.

A

Stress

101
Q

Which unit test starts with the terminal modules in the program?

a) Top-down
b) Non-incremental
c) Bottom-up
d) Incremental

A

c) Bottom-up

102
Q

___ testing starts with the terminal modules.

A

Bottum-up

103
Q

A ___ module is a module that does not call other modules.

A

terminal

104
Q

___ testing starts with the modules that call other modules.

A

Top-down

105
Q

In ___ testing, modules are individually tested.

A

non-incremental

106
Q

In the ___ testing process, modules are combined with the previously tested module.

A

Incremental

Software Quality Assurance (10 decks)

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