ISTQB chap 4 (part 2)

Front

Error Guessing is based on tester's knowledge except?

Back

How the application has implement in the past

Answer explanation

2. How the application has been implemented in the past:

   • This aspect is not directly related to error guessing. Error guessing focuses on anticipating errors based on common mistakes, past defects, and failures in similar applications, rather than the specific implementation history of the application. While understanding past implementations can be useful, it is not the primary basis for error guessing.

Front

Which of the following statements is the LEAST meaningful argument for using an ATDD approach with business process models for test case design?
- Testers will be able to show test coverage directly within the graphical representation of business processes
- 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
- 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

B. 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.

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

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

Front

Tests are simultaneously designed, executed, and evaluated while the tester learns about the test object in?

Back

Exploratory Testing

Front

"Exploratory testing is always performed using session-based testing to structure the testing"

Back

False

Answer explanation

Exploratory testing is a flexible approach where testers actively explore the application without predefined test cases. While session-based testing can be used to structure exploratory testing, it is not always required. Exploratory testing can be performed without any formal structure, depending on the context and goals of the testing effort.

Front

With high-level test conditions, in which stage are coverage items identified, exercised, and documented, ensuring comprehensive test coverage and traceability? Options: Create test, Debriefing session, Client retrospective, Test session

Back

Test session

Answer explanation

In a test session, especially within the context of exploratory testing, testers identify and exercise coverage items based on high-level test conditions. This stage involves actively exploring the application, executing tests, and observing the outcomes to ensure that various aspects of the application are covered.

Front

What is not a reason to update the checklist?

Back

Developers learn to avoid making the same errors

Answer explanation

• Checklist entries may become less effective over time: This is a valid reason to update the checklist to ensure it remains relevant and effective.

• Defect analysis identifies a root cause that occurs with high frequency: This is a valid reason to update the checklist to address recurring issues.

• Developers learn to avoid making the same errors: This is not a reason to update the checklist. While it's good that developers learn from past mistakes, the checklist itself doesn't need to be updated for this reason.

• Newly found high severity defects: This is a valid reason to update the checklist to include checks for new critical issues.

Front

Can checklist-based testing provide guidelines and some degree of consistency for the testing?

Back

True

Answer explanation

Checklist-based testing can indeed provide guidelines and some degree of consistency for the testing process. By following a checklist, testers ensure that they cover all necessary areas and maintain a consistent approach, which helps in identifying defects systematically.

Front

"The test cases must cover all the characteristics of the user story and should go beyond the story"

Back

False

Answer explanation

The test cases must cover all the characteristics of the user story but should not go beyond the story. They should be based on the acceptance criteria and focus on validating the specific requirements and scenarios described in the user story.

Front

What should the team do after creating positive test cases in the ATDD process?

Back

Perform negative testing

Front

As a [role], I want [____ to be accomplished], so that I can [resulting business value for the role]

Back

goal