random chapter 4

Question 1

A black-box test technique in which test cases are designed to exercise the combinations of conditions and the resulting actions shown in a decision table.

Answer 1

Decision table testing:

Question 2

A black-box test technique in which test cases are designed based on boundary values.

Answer 2

boundary value analysis:

Question 3

A black-box test technique in which test conditions are equivalence partitions exercised by one representative member of each partition

Answer 3

equivalence partitioning:

Question 4

A black-box test technique in which test cases are designed to exercise elements of a state transition model.

Answer 4

State transition testing:

Question 5

-Test techniques also help the tester to

Answer 5

define test conditions

identify coverage items

and identify test data during the test analysis and design

Question 6

Equivalence partitions can be identified for any data element related to the test object, including

Answer 6

inputs, outputs, configuration items, internal values, time-related values, and interface parameters.

Question 7

The partitions in equivalence partitions may be

Answer 7

continuous or discrete, ordered or unordered, finite or infinite. The partitions must not overlap and must be non-empty sets.

Question 8

Coverage is measured as the number of partitions exercised by at least one test case, divided by the total number of identified partitions, and is expressed as a percentage.

Answer 8

Equivalence partitions

Question 9

The simplest coverage criterion in the case of multiple sets of partitions is called :

-requires test cases to exercise each partition from each set of partitions at least once.

• does not take into account combinations of partitions.

Answer 9

Each Choice coverage

Question 10

are an effective way of recording complex logic, such as business rules.

Answer 10

Decision tables

Question 11

the conditions and the resulting actions of the system are defined. These form the rows of the table.

Answer 11

Decision tables

Question 12

Each column corresponds to a decision rule that defines a unique combination of conditions, along with the associated actions.

Answer 12

Decision tables

Question 13

The strength of this testing is that it provides a systematic approach to identify all the combinations of conditions, some of which might otherwise be overlooked.

Answer 13

Decision tables

Question 14

Its rows represent states, and its columns represent events (together with guard conditions if they exist).

Answer 14

State transition testing:

Question 15

the coverage items are executable statements.

Answer 15

statement testing

Question 16

The aim is to design test cases that exercise statements in the code until an acceptable level of coverage is achieved.

Answer 16

statement testing

Question 17

is a transfer of control between two nodes in the control flow graph, which shows the possible sequences in which source code statements are executed in the test object.

Answer 17

branch

Question 18

-Each transfer of control can be either unconditional (i.e., straight-line code) or conditional (i.e., a decision outcome).

Answer 18

branch testing

Question 19

-Branch coverage subsumes statement coverage.

Answer 19

This means that any set of test cases achieving 100% branch coverage also achieves 100% statement coverage (but not vice versa).

Question 20

error guessing: In general, errors, defects and failures may be related to:

Answer 20

input (e.g., correct input not accepted, parameters wrong or missing),

output (e.g., wrong format, wrong result)

logic (e.g., missing cases, wrong operator),

computation (e.g., incorrect operand, wrong computation),

interfaces (e.g., parameter mismatch, incompatible types),

or data (e.g., incorrect initialization, wrong type).

Question 21

are a methodical approach to the implementation of error guessing.

Answer 21

fault attack

Question 22

-This technique requires the tester to create or acquire a list of possible errors, defects and failures, and to design tests that will identify defects associated with the errors, expose the defects, or cause the failures.

-These lists can be built based on experience, defect and failure data, or from common knowledge about why software fails.

Answer 22

fault attack

Question 23

tests are simultaneously designed, executed, and evaluated while the tester learns about the test object.

Answer 23

Exploratory Testing

Question 24

Exploratory testing is sometimes conducted using this testing to structure the testing.

Answer 24

session-based testing

Question 25

In this approach, exploratory testing is conducted within a defined time-box.

Answer 25

session-based approach

Question 26

The tester uses a test charter containing test objectives to guide the testing.

Answer 26

session-based testing

Question 27

The test session is usually followed by a debriefing that involves a discussion between the tester and stakeholders interested in the test results of the test session.

Answer 27

session-based testing

Question 28

In this approach test objectives may be treated as high-level test conditions.

Answer 28

session-based testing

Question 29

The tester may use test session sheets to document the steps followed and the discoveries made.

Answer 29

session-based testing

Question 30

Exploratory testing will be more effective if the tester is

Answer 30

experienced,

has domain knowledge

has a high degree of essential skills, like analytical skills, curiosity and creativeness

Question 31

In this testing, a tester designs, implements, and executes tests to cover test conditions from a checklist.

Answer 31

In checklist-based testing,

Question 32

Checklists in checklist-based testing should not contain items that :

Answer 32

can be checked automatically,

items better suited as entry/exit criteria,

items that are too general

Question 33

Checklist items are often phrased in the form of a question.

It should be possible to check each item separately and directly.

These items may refer to:

Answer 33

requirements,
graphical interface properties,
quality characteristics
other forms of test conditions.

Question 34

Checklists can be created to support various test types, including these types of testing

Answer 34

functional and non-functional testing

Question 35

Some checklist entries may gradually become less effective over time because the developers will learn to avoid making the same errors.

New entries may also need to be added to reflect newly found high severity defects.

Therefore, checklists should be regularly updated based on

Answer 35

defect analysis.

However, care should be taken to avoid letting the checklist become too long.

Question 36

In the absence of detailed test cases, this testing can provide guidelines and some degree of consistency for the testing.

Answer 36

checklist-based testing

Question 37

Exploratory testing can incorporate the use of other test techniques

Answer 37

(e.g., equivalence partitioning, BVA, State transition testing ).

Question 38

represents a feature that will be valuable to either a user or purchaser of a system or software

Answer 38

user story

Question 39

User stories have three critical aspects (Jeffries 2000), called together the “3 C’s”:

Answer 39

Card – the medium describing a user story (e.g., an index card, an entry in an electronic board)


Conversation – explains how the software will be used (can be documented or verbal)


Confirmation – the acceptance criteria

Question 40

Collaborative authorship of the user story can use techniques such as

Answer 40

brainstorming and mind mapping.

Question 41

The collaboration allows the team to obtain a shared vision of what should be delivered, by taking into account three perspectives:

Answer 41

business,
development
and testing.

Question 42

Good user stories should be:

(INVEST).

Answer 42

Independent,
Negotiable,
Valuable,
Estimable,
Small
Testable

Question 43

this criteria for a user story are the conditions that an implementation of the user story must meet to be accepted by stakeholders.

Answer 43

Acceptance criteria

Question 44

Acceptance criteria are used to:

Answer 44

Define the scope of the user story

Reach consensus among the stakeholders

Describe both positive and negative scenarios

Serve as a basis for the user story
acceptance testing (see section 4.5.3)

Allow accurate planning and estimation

Question 45

There are several ways to write acceptance criteria for a user story. The two most common formats are:

Answer 45

Scenario-oriented (e.g., Given/When/Then format used in BDD, see section 2.1.3)


Rule-oriented (e.g., bullet point verification list, or tabulated form of input-output mapping)


Question 46

Test cases are created prior to implementing the user story.

Answer 46

Acceptance Test-driven Development (ATDD)

Question 47

Test cases may be executed manually or automated.

Answer 47

Acceptance Test-driven Development (ATDD)

Question 48

The first step is a specification workshop where the user story and (if not yet defined) its acceptance criteria are analyzed, discussed, and written by the team members.
Incompleteness, ambiguities, or defects in the user story are resolved during this process.

The next step is to create the test cases. This can be done by the team as a whole or by the tester individually.

The test cases are based on the acceptance criteria and can be seen as examples of how the software works.

Answer 48

Acceptance Test-driven Development (ATDD)

Question 49

Typically, the first test cases are positive, confirming the correct behavior without exceptions or error conditions, and comprising the sequence of activities executed if everything goes as expected.

Answer 49

Acceptance Test-driven Development (ATDD)

Question 50

Typically, test cases contain sentences in natural language involving the necessary preconditions (if any), the inputs, and the postconditions.

Answer 50

Acceptance Test-driven Development (ATDD)

Question 51

A collaboration-based test-first approach that defines acceptance tests in the stakeholders’ domain language.

Answer 51

Acceptance test-driven development-

Question 52

the criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

Answer 52

Acceptance criteria- T

Question 53

• An experience-based test technique in which test cases are designed to exercise the items of a checklist

Answer 53

Checklist-based testing

Question 54

An approach to testing that focuses on defect avoidance by collaborating among stakeholders

Answer 54

Collaboration-based test approach-

Question 55

The degree to which specified coverage items are exercised by a test suite, expressed as a percentage. Synonyms: test coverage

Answer 55

Coverage-

Question 56

An attribute or combination of attributes derived from one or more test conditions by using a test technique.

Answer 56

Coverage item-

Question 57

According to the ISTQB Glossary, the word ‘State Transition Testing’ is synonymous with which of the following words?

Answer 57

finite state testing

Question 58

this, in the context of collaborative user story writing is used to gather a diverse array of ideas and solutions from the team, encompassing different perspectives and expertise. This technique helps in creating rich and comprehensive user stories that reflect varied insights and needs.

Answer 58

Brainstorming

Question 59

Mind mapping is a collaborative technique well-suited for user story writing. Which of these activities is it

Answer 59

Identifying relationships between user stories and potential dependencies