iSQI CTFL-AT Practice Exam Dumps 2025

Agile software development is a software development approach whereby lines of code (production and/or test) of a component are written by two programmers sitting at a single computer

Agile software development tends to break a project into a number of iterations, where each iteration represents a separate phase of sequential development and thus in which testing is performed during the last iteration

Agile software development tends to adopt an iterative incremental lifecycle, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams

Agile software development tends to break a project into a series of increments, each of which delivers a portion of functionality through a series of mini-Waterfalls where all phases of the Waterfall are completed before proceeding to the next increment

Buy Now

Question 2

Consider an Agile project aimed at developing a test management tool. This tool allows Test Managers to generate progress reports for test analysis, test design and test execution phases in traditional projects. Consider the following user story of this Agile project:

"As a Test Manager who is looking at a progress report, I want to be able to print this progress report, so that I can keep a hard copy for my daily records."

For this user story the following acceptance criterion is defined:

"Given that I am a Test Manager looking at a progress report,

When I click the 'Print' button,

Then the progress report should be printed"

Based only on the given information, which of the following would you expect most likely to be true?

Options:

Both the user story and the acceptance criterion are expressed in adequate form, but the user story is not testable

Both the user story and the acceptance criterion are expressed in adequate form, but the user story does not describe functionality that is valuable to the user

During the conversation, the acceptance criterion should not be discussed since it is described using the Given-When-Then template

During the conversation, the need to update the acceptance criterion by specifying that a date stamp be visible on the printout could emerge

Question 3

You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customer's monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases, the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

Which of the following test cases can be treated as acceptance test criteria for the above user story?

1) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

2) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

3) As a customer assistant I can log in to the system and change my password.

4) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

5) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

6) As a bank manager I can log in to the system within 10 seconds.

Options:

Acceptance test criteria are 1, 2, 3 and 6

Acceptance test criteria are 1, 3, 4 and 5

Acceptance test criteria are 2, 4, 5 and 6

Acceptance test criteria are 1, 2, 4 and 5

Answer:

Explanation:

Acceptance test criteria are the conditions that a user story must satisfy to be accepted by the customer or the stakeholder. They are usually derived from the user story and its acceptance scenarios, and they should cover the functional and non-functional requirements of the user story. Acceptance test criteria should be clear, concise, testable, and agreed upon by the team and the customer or the stakeholder.

In this case, the user story describes the business rule for approving a loan request based on the customer’s income, repayment history, and loan amount. The user story also specifies the roles of the customer assistant and the bank manager in the process. Therefore, the acceptance test criteria should verify that the user story is implemented correctly and that the system behaves as expected for different scenarios and inputs.

The following test cases can be treated as acceptance test criteria for the above user story:

As a customer assistant I can log in to the system and check the history of the customer account for the last year. This test case verifies that the customer assistant can access the system and view the customer’s income information, which is one of the factors for approving the loan request.

As a customer assistant I can log in to the system and check the history of the customer debts and repayments. This test case verifies that the customer assistant can access the system and view the customer’s repayment history, which is another factor for approving the loan request.

As a bank manager I can log in to the system and receive the information of all requests waiting for approval. This test case verifies that the bank manager can access the system and see the list of loan requests that have been prepared by the customer assistant, and that the system provides the necessary information for each request.

As a bank manager I can log in to the system and decide whether to approve a loan for a customer. This test case verifies that the bank manager can access the system and perform the approval action for a loan request, and that the system applies the business rule correctly and updates the status of the request accordingly.

The following test cases cannot be treated as acceptance test criteria for the above user story:

As a customer assistant I can log in to the system and change my password. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a generic test case that applies to any user of the system, not specific to the customer assistant role or the loan approval process.

As a bank manager I can log in to the system within 10 seconds. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a performance test case that applies to any user of the system, not specific to the bank manager role or the loan approval process.

[: ISTQB® Foundation Level Agile Tester Syllabus1, Section 2.3.1, pages 15-16; ISTQB® Glossary of Testing Terms2, version 4.0, pages 2 and 3., ]

Week End Sale 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: save70

CTFL-AT Exam Dumps : Certified Tester Foundation Level Agile Tester

iSQI Related Exams

Verified By IT Certified Experts

CertsTopics.com Certified Safe Files

Up-To-Date Exam Study Material

99.5% High Success Pass Rate

100% Accurate Answers

Instant Downloads

Exam Questions And Answers PDF

Try Demo Before You Buy

Certified Tester Foundation Level Agile Tester Questions and Answers

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

Options:

Answer:

Explanation:

CompTIA

Fortinet

Microsoft

Salesforce