CEN MIDTERM STUDY GUIDE Flashcards
1
Q
What should be tested in a State-Transition Diagram?
A
Every transition
2
Q
What combinations are listed in a State-Transition Table?
A
All possible valid and invalid state-transition combinations
3
Q
What are the columns in a State-Transition Table?
A
Current State, Event, Action, and Next State
4
Q
Should a State-Transition Diagram represent multiple entities?
A
Should not
5
Q
Do Events have parameters?
A
May have parameters that are related to them
6
Q
What is an Event?
A
Something that causes the system to change state
7
Q
What is a Transition?
A
A change from one state to another caused by an event
8
Q
What is a State?
A
A condition in which a system is waiting for one or more events
9
Q
Are State-Transition Diagrams helpful for capturing the order of events?
A
True
10
Q
What are State-Transition Diagrams used for?
A
Document system events and responses
11
Q
When is Pairwise Testing a good option?
A
When the number of combinations to test is very large
12
Q
Are Orthogonal Array and Allpairs combinations the same?
A
May not be the same
13
Q
What is Allpairs?
A
An algorithm that generates the pairs directly without using an external device like an orthogonal array
14
Q
How do you choose the right Orthogonal Array size?
A
Exact match or bigger
15
Q
What can be done with extra columns in an Orthogonal Array?
A
Delete them
16
Q
What is the first step in using Orthogonal Arrays for testing?
A
Identify the variables
17
Q
What does L18(3721) represent in an Orthogonal Array?
A
18 rows, 7 columns with 3 values, 1 column with 2 values
18
Q
What is an Orthogonal Array?
A
A two-dimensional array of numbers where any two columns contain all combinations in every column pair
19
Q
Does Pairwise Testing choose all important test cases?
A
May not choose important test cases
20
Q
What is Pairwise Software Testing?
A
A method of software testing that tests all possible discrete combinations of each pair of input parameters
21
Q
What values should be chosen when conditions are based on ranges?
A
Values at the boundaries
22
Q
What happens if a decision table is missing a combination?
A
The system may not work correctly
23
Q
Who can benefit from decision tables?
A
Business analysts, designers, software programmers, and software testers
24
Q
What is the number of combinations with two binary conditions?
A
4
25
How should test cases be created from decision tables?
Label conditions as inputs, actions as expected results, and rules as test cases
26
How many test cases should be created for each rule?
At least one
27
What can tables have in terms of actions?
Unique actions or shared actions with other rules
## Footnote
This simplifies the table
28
How Many Test Cases Should Be Created for Each Rule?
Create at least one.
## Footnote
Every rule in a decision table should be tested to ensure verification.
29
What Actions Can Each Rule Specify?
An action unique to that rule, or rules may share actions.
## Footnote
Rules can have unique actions or share actions to simplify the table.
30
Can Decision Tables Specify More Than One Action Per Rule?
False.
## Footnote
Each rule can specify multiple actions, allowing complex outcomes.
31
What Do Decision Tables Represent?
Business rules based on conditions and actions.
## Footnote
Define how various conditions lead to specific actions.
32
What Are Decision Tables Used For?
Capture system requirements and system design.
## Footnote
Provides a structured way to document how conditions impact system behavior.
33
Is Boundary Value Testing Applicable to Input Length and Type?
True.
## Footnote
Applies to input lengths and types, like string length or data type constraints.
34
Do Additional Test Cases Within the Same Equivalence Class Discover Defects?
Rarely.
## Footnote
Once boundary values are tested, other inputs within the same range generally behave the same.
35
What Are the Steps for Boundary Value Testing?
Identify the equivalence classes, identify the boundaries of each equivalence class, create test cases for each boundary value.
## Footnote
These steps ensure comprehensive coverage of edge cases.
36
What Is the Most Efficient Way to Find Boundary Defects?
Inspection.
## Footnote
Reviews of requirements and code can detect potential boundary defects.
37
Can Defects Be in Both Software Requirements and Code?
True.
## Footnote
Misunderstandings or incorrect implementations can introduce errors.
38
What Are Boundary Values for This Age Logic?
{-1, 0, 1}.
## Footnote
Boundary values should cover just below, on, and just above specified limits.
39
Are Individual Tests Often Created for Every System Input Boundary Value?
False.
## Footnote
It’s impractical to test every possible boundary value.
40
When Is Boundary Value Testing Most Appropriate?
When the input is a continuous range of values.
## Footnote
Continuous ranges are prone to defects at edges.
41
How Should You Choose Test Points for Boundary Values?
On, just below, and just above the boundary.
## Footnote
Ensures coverage of potential edge cases.
42
What Does Boundary Value Testing Focus On?
The boundaries, since that is where many defects occur.
## Footnote
Testing boundary points ensures robust software behavior.
43
Does Equivalence Class Testing Reduce Test Cases?
Yes, it can significantly reduce the number of test cases.
## Footnote
Focuses on representative values to avoid redundant tests.
44
At What Levels Can Equivalence Class Testing Be Used?
Unit, integration, system, and acceptance.
## Footnote
Applies at every stage of testing.
45
Is Testing Multiple Inputs Simultaneously Efficient?
Yes, it is generally more efficient.
## Footnote
Combining inputs in one test can save time if each combination is meaningful.
46
Is Testing Invalid Values One by One a Good Approach?
Yes.
## Footnote
Allows you to pinpoint which input causes errors, improving debugging.
47
Is a Test Case with All Invalid Data a Good Approach?
No.
## Footnote
A single test with only invalid data doesn't reveal which specific input causes a failure.
48
Do We Have Time to Test Every Equivalence Class?
Rarely.
## Footnote
Testing every equivalence class is impractical; focus on representative test cases.
49
What are Valid Values in a Continuous Range?
Valid values when inputs range from 1000 to 5000 could include 1500, 1600, 1700.
## Footnote
Requires selecting representative values for edge cases and typical inputs.
50
What is Defensive Testing?
A testing approach that defines tests for both normal and abnormal pre-conditions.
## Footnote
Ensures software behaves correctly in unexpected situations.
51
What is Testing-by-Contract?
An approach to create test cases only for situations required by the module to complete its promises.
## Footnote
Focuses on ensuring a module works as specified.
52
What is an Equivalence Class?
A set of data that is treated the same by the module or produces the same result.
## Footnote
Groups inputs that should lead to similar behavior or outputs.
53
What is Acceptance Testing?
Testing that will result in the customer accepting the software for implementation.
## Footnote
Validates the software meets all agreed-upon requirements.
54
What are Regression Test Suites?
Run the program and compare the output to the results of the same tests run against a previous version.
## Footnote
Ensures changes haven’t broken existing functionality.
55
What are Outputs in testing?
Information displayed on screen, sent to other systems, written to files or databases.
## Footnote
Every output should be tested against expectations.
56
What are Inputs in testing?
Data entered using the keyboard, files, or databases.
## Footnote
Testing should include various types of inputs: valid, invalid, boundary, and empty values.
57
What are the components of Well-Designed Test Cases?
Inputs, Outputs, Order of Execution.
## Footnote
Inputs are data fed into the system, outputs are the results, and order of execution ensures test accuracy.
58
What are Test Cases?
Specified conditions used in the process of software testing.
## Footnote
Effective test cases include a title, description, test data, expected outcomes, and preconditions.
59
What are the 4 Levels of Testing?
Unit, Integration, System, and Acceptance.
## Footnote
Each level serves a different purpose: testing components, module interactions, the entire application, and user/business requirements respectively.
60
What is White Box Testing?
A strategy in which testing is based on the internal paths, structure, and implementation of the software under test.
## Footnote
Involves analyzing code and creating test cases for specific paths.
61
What is Black Box Testing?
A strategy in which testing is based solely on the requirements and specifications.
## Footnote
Tester focuses on inputs and expected outputs without concern for internal workings.
62
What is Testing?
The process of comparing what is with what ought to be.
## Footnote
Identify the business requirements, define expected behavior, and run test cases to check for discrepancies.
63
Every transition
What should be tested in a State-Transition Diagram?
64
All possible valid and invalid state-transition combinations
What combinations are listed in a State-Transition Table?
65
Current State, Event, Action, and Next State
What are the columns in a State-Transition Table?
66
Should not
Should a State-Transition Diagram represent multiple entities?
67
May have parameters that are related to them
Do Events have parameters?
68
Something that causes the system to change state
What is an Event?
69
A change from one state to another caused by an event
What is a Transition?
70
A condition in which a system is waiting for one or more events
What is a State?
71
True
Are State-Transition Diagrams helpful for capturing the order of events?
72
Document system events and responses
What are State-Transition Diagrams used for?
73
When the number of combinations to test is very large
When is Pairwise Testing a good option?
74
May not be the same
Are Orthogonal Array and Allpairs combinations the same?
75
An algorithm that generates the pairs directly without using an external device like an orthogonal array
What is Allpairs?
76
Exact match or bigger
How do you choose the right Orthogonal Array size?
77
Delete them
What can be done with extra columns in an Orthogonal Array?
78
Identify the variables
What is the first step in using Orthogonal Arrays for testing?
79
18 rows, 7 columns with 3 values, 1 column with 2 values
What does L18(3721) represent in an Orthogonal Array?
80
A two-dimensional array of numbers where any two columns contain all combinations in every column pair
What is an Orthogonal Array?
81
May not choose important test cases
Does Pairwise Testing choose all important test cases?
82
A method of software testing that tests all possible discrete combinations of each pair of input parameters
What is Pairwise Software Testing?
83
Values at the boundaries
What values should be chosen when conditions are based on ranges?
84
The system may not work correctly
What happens if a decision table is missing a combination?
85
Business analysts, designers, software programmers, and software testers
Who can benefit from decision tables?
86
4
What is the number of combinations with two binary conditions?
87
Label conditions as inputs, actions as expected results, and rules as test cases
How should test cases be created from decision tables?
88
At least one
How many test cases should be created for each rule?
89
Unique actions or shared actions with other rules
## Footnote
This simplifies the table
What can tables have in terms of actions?
90
Create at least one.
## Footnote
Every rule in a decision table should be tested to ensure verification.
How Many Test Cases Should Be Created for Each Rule?
91
An action unique to that rule, or rules may share actions.
## Footnote
Rules can have unique actions or share actions to simplify the table.
What Actions Can Each Rule Specify?
92
False.
## Footnote
Each rule can specify multiple actions, allowing complex outcomes.
Can Decision Tables Specify More Than One Action Per Rule?
93
Business rules based on conditions and actions.
## Footnote
Define how various conditions lead to specific actions.
What Do Decision Tables Represent?
94
Capture system requirements and system design.
## Footnote
Provides a structured way to document how conditions impact system behavior.
What Are Decision Tables Used For?
95
True.
## Footnote
Applies to input lengths and types, like string length or data type constraints.
Is Boundary Value Testing Applicable to Input Length and Type?
96
Rarely.
## Footnote
Once boundary values are tested, other inputs within the same range generally behave the same.
Do Additional Test Cases Within the Same Equivalence Class Discover Defects?
97
Identify the equivalence classes, identify the boundaries of each equivalence class, create test cases for each boundary value.
## Footnote
These steps ensure comprehensive coverage of edge cases.
What Are the Steps for Boundary Value Testing?
98
Inspection.
## Footnote
Reviews of requirements and code can detect potential boundary defects.
What Is the Most Efficient Way to Find Boundary Defects?
99
True.
## Footnote
Misunderstandings or incorrect implementations can introduce errors.
Can Defects Be in Both Software Requirements and Code?
100
{-1, 0, 1}.
## Footnote
Boundary values should cover just below, on, and just above specified limits.
What Are Boundary Values for This Age Logic?
101
False.
## Footnote
It’s impractical to test every possible boundary value.
Are Individual Tests Often Created for Every System Input Boundary Value?
102
When the input is a continuous range of values.
## Footnote
Continuous ranges are prone to defects at edges.
When Is Boundary Value Testing Most Appropriate?
103
On, just below, and just above the boundary.
## Footnote
Ensures coverage of potential edge cases.
How Should You Choose Test Points for Boundary Values?
104
The boundaries, since that is where many defects occur.
## Footnote
Testing boundary points ensures robust software behavior.
What Does Boundary Value Testing Focus On?
105
Yes, it can significantly reduce the number of test cases.
## Footnote
Focuses on representative values to avoid redundant tests.
Does Equivalence Class Testing Reduce Test Cases?
106
Unit, integration, system, and acceptance.
## Footnote
Applies at every stage of testing.
At What Levels Can Equivalence Class Testing Be Used?
107
Yes, it is generally more efficient.
## Footnote
Combining inputs in one test can save time if each combination is meaningful.
Is Testing Multiple Inputs Simultaneously Efficient?
108
Yes.
## Footnote
Allows you to pinpoint which input causes errors, improving debugging.
Is Testing Invalid Values One by One a Good Approach?
109
No.
## Footnote
A single test with only invalid data doesn't reveal which specific input causes a failure.
Is a Test Case with All Invalid Data a Good Approach?
110
Rarely.
## Footnote
Testing every equivalence class is impractical; focus on representative test cases.
Do We Have Time to Test Every Equivalence Class?
111
Valid values when inputs range from 1000 to 5000 could include 1500, 1600, 1700.
## Footnote
Requires selecting representative values for edge cases and typical inputs.
What are Valid Values in a Continuous Range?
112
A testing approach that defines tests for both normal and abnormal pre-conditions.
## Footnote
Ensures software behaves correctly in unexpected situations.
What is Defensive Testing?
113
An approach to create test cases only for situations required by the module to complete its promises.
## Footnote
Focuses on ensuring a module works as specified.
What is Testing-by-Contract?
114
A set of data that is treated the same by the module or produces the same result.
## Footnote
Groups inputs that should lead to similar behavior or outputs.
What is an Equivalence Class?
115
Testing that will result in the customer accepting the software for implementation.
## Footnote
Validates the software meets all agreed-upon requirements.
What is Acceptance Testing?
116
Run the program and compare the output to the results of the same tests run against a previous version.
## Footnote
Ensures changes haven’t broken existing functionality.
What are Regression Test Suites?
117
Information displayed on screen, sent to other systems, written to files or databases.
## Footnote
Every output should be tested against expectations.
What are Outputs in testing?
118
Data entered using the keyboard, files, or databases.
## Footnote
Testing should include various types of inputs: valid, invalid, boundary, and empty values.
What are Inputs in testing?
119
Inputs, Outputs, Order of Execution.
## Footnote
Inputs are data fed into the system, outputs are the results, and order of execution ensures test accuracy.
What are the components of Well-Designed Test Cases?
120
Specified conditions used in the process of software testing.
## Footnote
Effective test cases include a title, description, test data, expected outcomes, and preconditions.
What are Test Cases?
121
Unit, Integration, System, and Acceptance.
## Footnote
Each level serves a different purpose: testing components, module interactions, the entire application, and user/business requirements respectively.
What are the 4 Levels of Testing?
122
A strategy in which testing is based on the internal paths, structure, and implementation of the software under test.
## Footnote
Involves analyzing code and creating test cases for specific paths.
What is White Box Testing?
123
A strategy in which testing is based solely on the requirements and specifications.
## Footnote
Tester focuses on inputs and expected outputs without concern for internal workings.
What is Black Box Testing?
124
The process of comparing what is with what ought to be.
## Footnote
Identify the business requirements, define expected behavior, and run test cases to check for discrepancies.
What is Testing?
