Online Access Free CTFL-AcT Exam Questions

Assume you are testing functionality of the interface of an elevator. One of the requirements is that the elevator can work only if the total weight of the passengers does not exceed 200 kg. The elevator can reach the following floors: Ground Floor, 1st floor and 2nd floor. You want to create an acceptance test using the Gherkin language. You can use the following phrases for this purpose:
i.the total weight of passengers is greater than 200 kg
ii.the elevator is on the Ground Floor
iii.a button '1st floor' was pressed
iv.the elevator goes to the 1st floor
v.a passenger standing at the 2nd floor calls the elevator
vi.a message 'too many passengers' is displayed on the screen
Which of the following statements correctly matches constructs of Given/When/Then with a relevant phrase in order to create a correct test case for the given requirement?

• A.GIVEN ii)
  WHEN i)
  THEN vi)
• B.GIVEN iii)
  WHEN ii)
  THEN iv)
• C.GIVEN ii)
  WHEN v) AND vi) THEN i)
• D.GIVEN ii)
  WHEN iv)
  THEN v)

Assume you would like to create a model describing a loan request process in a bank.
The loan request process starts when the customer submits a loan application. The bank then reviews the application. Regardless of whether the loan request is approved or not, a letter is sent to inform the customer of the decision. If the request is approved, the loan contract is created.
You have drawn the following business process model using BPMN 2.0.

Which one of the following sentences is true with respect to this process model?

• A.A review credit report is optional when reviewing the loan application.
• B.Performing title search and requesting credit report are sequential tasks.
• C.Creating the loan contract is defined as a sub-process.
• D.Verifying employment is not done when the loan status is rejected.

Which of the following sentences explains BEST how acceptance test cases can be derived from the acceptance criteria

• A.Risk-based testing is not a good practice for designing and prioritizing tests because the objective is to cover only the acceptance criteria
• B.Test design should start with non-functional acceptance criteria and only then with functional aspects
• C.Acceptance criteria are not useful for creating acceptance test cases because experience-based techniques should be preferred
• D.Test techniques such as business process-based testing or use case testing can be used to create acceptance tests from the acceptance criteria

On a project to develop an event booking platform, a review session is being conducted on acceptance test cases written in Ghenkin's language. Consider the following test case:
1. GIVEN I am logged in on the event booking platform
2. AND I have selected an event from the list displayed for the "live concert" category
3. WHEN I click "Buy Tickets" buttom
4. AND I enter "3" into "Ticket quantify" field
5. AND I agree on terms and conditions
6. THEN The system should display the checkout page
7. AND I should provide my personal data for payment and eticket delivery Which of the following sentences MOST closely corresponds to a comment that could be made on this test case during the review?

• A.This test case is perfectly written
• B.Line 3 refers to an element to the user interface, which is to be avoided and line 7 is and action and not a result
• C.Line 3 refers to and element of the user interface which is to be avoided, line 4 the quantity should not be set and line 7 is an action and not a result
• D.The "When" part lacks an action to enter number of tickets request that is greater than the limit allowed per person

Which one of the following statements BEST explains how the quality of requirements / user stories and acceptance criteria affects acceptance testing?

• A.Testers may complete unclear requirements by assumptions, as login as they discuss those assumptions with at least one stakeholder
• B.INVEST is a technique that ensure the quality of user stories or requirements, thus replacing regular reviews
• C.Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing
• D.In Agile development lifecycle models, requirement engineering becomes less important due to the product owner role.