iSQI CTFL-AcT ISTQB Foundation Level - Acceptance Testing Exam Practice Test

Information to evaluate the level of risk for product release.

Technical details on defect fixes.

Test strategy and test design methods.

Test procedure information.

In a model-based testing approach, acceptance tests are generated from graphical or textual models.

In a priority-based testing approach, prioritization of acceptance tests depends on identified product risks.

In a risk-based testing approach, acceptance criteria are derived from the tester’s experience and intuition.

In a black-box testing approach, acceptance test scenarios follow the implemented sequence of function calls in the code.

Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing.

In Agile development lifecycle models, requirement engineering becomes less important due to the product owner role.

INVEST is a technique that ensure the quality of user stories or requirements, thus replacing regular reviews.

Testers may complete unclear requirements by assumptions, as long as they discuss those assumptions with at least one stakeholder.

Indicating that the tester should take the role of a novice user can be part of an exploratory test charter.

The test charter is elaborated during the testing session according to test execution results.

Each exploratory test charter is based on a previously defined list of activities that would be interesting to test.

Acceptance testers use the exploratory test charter during the testing session to define the test oracle.

Business analysts collaborate on test planning and risk analysis to ensure that further on, appropriate test cases are developed and prioritized.

Business analysts usually cannot review acceptance tests, because they do not understand the technical details.

Testers participate in identifying business needs of stakeholders to better understand the business needs and related requirements.

Once the requirements and acceptance criteria have been defined, business analysts are no longer involved in testing activities.

static code analysis

input validation

equivalence partitioning

defect-based test design