Loading, please wait ...
Open its course - Software Quality Engineering

Error guessing

Topic Questions:
34
MCQs T/F FiB SQ
12
12
0
12
12
0
10
10
0
0
0
0
Question Type Legends

Easy

Medium

Difficult

Multiple Choice Questions for Error guessing

  • 1 In the overall test-case-design strategy, Error Guessing is applied to check which of the following?
    1. The internal control flow of the program logic.
    2. That 100% of the source code statements are executed.
    3. Special cases that may have been overlooked when the program was designed.
    4. The network latency between distributed servers.

  • 2 Error Guessing is categorized as which type of testing methodology in Software Quality Engineering?
    1. White-box testing
    2. Static analysis
    3. Black-box testing
    4. Non-incremental testing

  • 3 Why is it difficult to define a formal procedure for the Error Guessing technique?
    1. Because it requires advanced mathematical proofs to validate.
    2. Because it is largely an intuitive and subjective process based on a tester's 'knack'.
    3. Because it is only applicable to hardware testing environments.
    4. Because it is an automated process performed by compilers.

  • 4 For testing a binary-search subroutine, which table size is considered an error-prone situation by Error Guessing?
    1. A size that is a multiple of 100.
    2. A size that is a prime number.
    3. A size that is one less than or one greater than a power of two.
    4. A size that remains constant across all test runs.

  • 5 When using error guessing to test a sorting subroutine, which of the following is a recommended situation to explore?
    1. A list containing 50 random unique integers.
    2. An input list that is already sorted.
    3. A list with alternating even and odd numbers.
    4. A list containing only prime numbers.

  • 6 In the 'spirit' of Error Guessing, what should a tester look for when reading a software specification?
    1. The exact word count of the requirements document.
    2. Spelling and grammatical mistakes in the title record.
    3. Assumptions that the programmer might have made that were omitted from the specs.
    4. Direct translations of every requirement into a database schema.

  • 7 According to the recommended strategy, Error Guessing should be used to add test cases after which other methods?
    1. Logic coverage and path coverage testing.
    2. Statement coverage and code inspections.
    3. Boundary-Value Analysis and Equivalence Partitioning.
    4. Random testing and alpha site testing.

  • 8 When testing a variable number of inputs (such as entries in a list), which specific cases does Error Guessing suggest are error-prone?
    1. Lists containing more than 100 unique alphanumeric entries.
    2. The cases of 'none' and 'one' (e.g., empty or single-entry lists).
    3. Only lists that have an even number of total entries.
    4. Inputs that use lowercase letters instead of uppercase letters.

  • 9 Which of the following is identified as a classic 'error-prone situation' to explore using Error Guessing?
    1. The presence of a 0 value in a program’s input or output.
    2. A middle-range value within a large valid dataset.
    3. An input that perfectly adheres to the 'sunny-day' scenario.
    4. Any input that strictly follows the explicitly defined specification.

  • 10 What is the primary characteristic of the 'Error Guessing' technique in software testing?
    1. It follows a rigid mathematical model for automated test generation.
    2. It is an intuitive and ad hoc process based on the tester's experience.
    3. It is a white-box technique that requires access to internal source code.
    4. It relies solely on random input generators to identify system faults.

  • 11 Which of the following method does not follow any specific method and identify test cases randomly based on the experience of the test engineer.
    1. Equivalence Partition
    2. Error Guessing
    3. Both
    4. None

  • 12 Black box test cases identification methodology ______________, enumerate a list of possible errors or error-prone situations and then write test cases based on the list.
    1. Equivalence Partition
    2. Boundary value analysis
    3. Cause Effect Graphing
    4. Error Guessing

Contact Us

support@subexpert.com
Write to Us View Help
Subject Expert Logo

Subject Expert

Learning Experience Platform

Follow Us
Facebook Switch Display Mode Enable Translation
© 2026 - Subject Expert)