Chapter 4 - 4.4-4.5 Flashcard

Front

Which of the following is a true statement about exploratory testing?

Back

More experienced testers who have tested similar applications and technologies are likely to do better than less experienced testers at exploratory testing.

Answer explanation

1. Exploratory testing often uncovers additional tests.

3. It can involve both black-box and white-box techniques.

5. The time for exploratory testing can be planned and controlled.

Front

What is error guessing?

Back

A testing technique used to guess where a developer is likely to have made a mistake.

Front

Which of the following statements about error guessing are True? A. Error guessing uses a test charter and test session sheets B. Error guessing is based on tester knowledge C. Error guessing always uses a checklist D. Error guessing is a black-box test technique E. Error guessing can be based on mistakes developers may make

Back

B and E

Answer explanation

• B. Error guessing is based on tester knowledge: Relies on the tester's experience, intuition, and knowledge of common mistakes.

• E. Error guessing can be based on mistakes developers may make: Uses understanding of typical developer errors to anticipate issues.

• Why the others are not true:

  A: More informal and intuitive, doesn't use structured documents like test charters.

• C: Doesn't always rely on checklists; it's about intuition and experience.

• D: Not limited to black-box testing; can involve understanding the code.

Front

Which of the following BEST matches the descriptions with the Experience test techniques? Tests are based on defects' likelihood and their distribution, The processing within the test object is checked, Deviations from the requirements are checked, Coverage is measured based on a selected structure of the test object

Back

Tests are based on defects' likelihood and their distribution

Answer explanation

Tests are based on defects' likelihood and their distribution is correct because experience-based testing uses knowledge of past defects to focus on areas where errors are most likely to occur

1. Processing within the test object: Related to white-box testing.

2. Deviations from requirements: Requirements-based testing.

3. Coverage based on structure: Structural or coverage-based testing.

Front

How do experience-based test techniques differ from black-box test techniques?

Back

They depend on an individual's domain knowledge and expertise rather than on a documented record of what the system should do.

Answer explanation

They depend on an individual's domain knowledge and expertise rather than on a documented record of what the system should do.

Why the others are not true:

1. Documented record: Black-box techniques rely on this, not experience-based.

3. Older testers: Experience-based techniques depend on expertise, not age.

5. System structure: This is more related to white-box testing.

Front

Which of the following statements BEST explains experience-based testing?

Back

If the testers are experienced and have good knowledge of the system under test, experience-based techniques are a viable alternative to more formal techniques if there are problems with the quality of the documentation or if the project is under a tight schedule.

Answer explanation

Experience-based techniques rely on the tester's knowledge and experience and can therefore be used to increase the coverage as the tester knows which areas need more testing.

Why the others are not correct:

1. Alternative to formal techniques: Experience-based testing complements formal techniques but isn't a direct alternative.

3. Using checklists: Checklists can help, but experience-based testing doesn't replace black-box techniques.

5. Used if no suitable formal techniques: Experience-based testing is valuable even when formal techniques are available.

Front

Which of the following BEST describes the collaborative approach to user story writing? Options: User stories are created by business representatives, developers, and testers together.

Back

User stories are created by business representatives, developers, and testers together.

Answer explanation

User stories are created by business representatives, developers, and testers together:

This approach ensures that all perspectives are considered, leading to more comprehensive and effective user stories. It fosters collaboration and communication among all stakeholders, which is crucial for successful agile development

User stories are created by business representatives and verified by developers and testers:

This approach implies a sequential process rather than a collaborative one. It suggests that business representatives create the stories first, and then developers and testers verify them, which can lead to miscommunication and gaps in understanding.

User stories are created by testers and developers and then accepted by business representatives:

Similar to the first option, this approach is also sequential. It suggests that testers and developers create the stories first, and then business representatives accept them. This can result in user stories that may not fully capture the business requirements or user needs.

User stories are created in a way that they are independent, negotiable, valuable, estimable, small, and testable:

This option describes the characteristics of good user stories (often referred to by the acronym INVEST), but it does not address the collaborative aspect of the creation process. While these characteristics are important, they do not specify who is involved in writing the stories.

Front

Your company wants to establish a new human resources management application. As a tester, you propose to use an ATDD approach and to use business process models for test case design. Which of the following statements is the LEAST meaningful argument for this approach? Business process models will make it easier to detect defects in the application code, As business process models will be updated to maintain the tests, they will be living documentation of the product, Testers will be able to show test coverage directly within the graphical representation of business processes, The process models will help testers understand the use cases to be tested

Back

Business process models will make it easier to detect defects in the application code.

Answer explanation

It's the least meaningful because business process models help understand workflows, not directly find code defects.

Why the others are more meaningful:

1. Living documentation: Business process models provide up-to-date documentation.

3. Test coverage: Graphical representation helps visualize test coverage.

5. Understanding use cases: Models help testers understand what needs to be tested.

Front

For which of the following situations is exploratory testing suitable? When the system is developed incrementally, and no test charter is available, When an advanced knowledge of the system already exists, and evidence is to be if it should be tested intensively, When testers are available who have enough knowledge of similar applications and technologies, When time pressure requires speeding up the execution of tests already specified

Back

When testers are available who have enough knowledge of similar applications and technologies

Answer explanation

Exploratory testing uses the tester's experience, intuition, and knowledge to find defects that traditional methods might miss. Testers can adapt their approach on the fly to identify issues.

Less Suitable Situations:

• Incremental development without a test charter: A test charter provides direction and focus.

• Advanced system knowledge needing intensive testing: Requires structured testing, not exploratory.

• Time pressure to execute pre-specified tests: Pre-specified tests are faster than exploratory testing.

Front

Which of the following BEST matches the descriptions with the White-box test techniques? Tests are based on defects' likelihood and their distribution, The processing within the test object is checked, Deviations from the requirements are checked, User stories are used as the test basis

Back

The processing within the test object is checked

Answer explanation

White-box testing examines the internal structure, design, and code to verify input/output flow and functionality of loops, statements, and paths.

Less Suitable Descriptions:

• Defects' likelihood and distribution: Fits experience-based testing.

• Deviations from requirements: Related to requirements-based testing.

• User stories as test basis: Aligns with agile testing.