Exploratory Testing Heuristics and Test Oracles

Question 1

What does the acronym 'FEW HICCUPS' primarily help exploratory testers identify?

Accepted Answer

Test oracle heuristics for recognizing problems in a product

Answer

A set of session time management guidelines

Answer

Charter writing templates for test sessions

Answer

Defect severity classification criteria

Question 2

In exploratory testing, a 'test oracle' is best described as:

Accepted Answer

A mechanism for determining whether a test has passed or failed

Answer

An automated tool that generates test cases

Answer

A senior tester who approves defect reports

Answer

A database of pre-approved expected outcomes

Question 3

Which heuristic in HICCUPPS involves comparing the product under test against competing or similar products?

Accepted Answer

Comparable Products

Answer

History

Answer

Image

Answer

Claims

Question 4

When using the 'History' oracle heuristic, a tester primarily compares:

Accepted Answer

The current product version against previous versions

Answer

Test results against industry compliance standards

Answer

Actual output against user documentation

Answer

Current defects against archived bug databases

Question 5

The 'Claims' oracle heuristic involves comparing the product's behavior against:

Accepted Answer

Marketing materials, manuals, and stated requirements

Answer

Internal source code comments

Answer

Competitor product feature lists

Answer

Historical defect frequency data

Question 6

A 'blind oracle' problem in testing occurs when:

Accepted Answer

There is no reliable reference to determine whether observed behavior is correct

Answer

Testers lack domain knowledge to evaluate the application

Answer

Automated tools cannot detect visual rendering defects

Answer

The tester is unfamiliar with the testing environment

Question 7

The HICCUPPS mnemonic (as described by Michael Bolton and James Bach) includes which of the following as one of its oracle heuristics?

Accepted Answer

History, Image, Comparable Products, Claims, User Expectations, Product, Procedures, Standards

Answer

History, Implementation, Code, Claims, Users, Products, Processes, Systems

Answer

Heuristics, Integration, Compatibility, Claims, Usability, Performance, Portability, Security

Answer

History, Interface, Correctness, Compatibility, Usability, Performance, Portability, Standards