Exploratory Testing Heuristics and Test Oracles 2

Question 1

What is the primary purpose of using heuristics in exploratory testing?

Accepted Answer

To guide test idea generation and problem recognition efficiently

Answer

To fully replace formal test plans in all projects

Answer

To automate repetitive regression test scenarios

Answer

To produce compliance documentation for audits

Question 2

In the context of test oracles, 'consistency oracles' check whether:

Accepted Answer

The product behaves consistently with standards, history, claims, or comparable products

Answer

The product produces the same output every time under identical conditions

Answer

Automated test scripts produce consistent pass/fail results across runs

Answer

Testers follow consistent procedures during each session

Question 3

The 'Image' heuristic in FEW HICCUPS asks the tester to consider:

Accepted Answer

Whether the product's behavior matches the organization's brand and reputation expectations

Answer

Whether all image files and graphics render correctly

Answer

Whether the UI design meets visual accessibility standards

Answer

Whether screenshot evidence documents the defect clearly

Question 4

When a tester applies the 'Explainability' heuristic from FEW HICCUPS, they are asking:

Accepted Answer

Would I be able to explain this product behavior to a user without embarrassment?

Answer

Can I explain the test case steps clearly in a test report?

Answer

Can the development team explain the root cause of this behavior?

Answer

Is this defect description explainable in a formal defect tracking system?

Question 5

Which of the following is NOT included in the FEW HICCUPS oracle heuristics?

Accepted Answer

Efficiency

Answer

Familiar

Answer

World

Answer

Standards

Question 6

Which type of oracle is generally considered most authoritative when determining whether software behavior is correct?

Accepted Answer

Specification oracle

Answer

Heuristic oracle

Answer

Sampling oracle

Answer

Statistical oracle

Question 7

The 'Familiar' heuristic in FEW HICCUPS prompts a tester to ask:

Accepted Answer

Does this behavior match common software patterns and conventions I've seen before?

Answer

Is this feature familiar to the members of the test team?

Answer

Is this test scenario one I have executed in a previous session?

Answer

Is the user interface familiar to the end-user audience?