ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 1:

  Which of the following describes the frequency with which usually all changes made to the software are merged and all changed components are integrated regularly in a continuous integration process?

  A. At least once per iteration
  B. At least once a week
  C. At least once a month
  D. At least once a day
  D. At least once a day

  ---

  From the CTFL-AT Syllabus v4.0, Section 4.2 Continuous Integration, it states: "Continuous integration involves integrating code into a shared repository several times a day. Each integration is verified by an automated build and automated tests."

  Hence, Option D at least once a day correctly reflects best practice in continuous integration.

  Option A (once per iteration) and B C, are far too infrequent to meet the goals of CI. The objective is to detect integration issues early and often, which is only achievable through daily (or more frequent) integrations.

  References:

  CTFL-AT Syllabus v4.0, Section 4.2 Learning Objective (K2) . Understand frequency and purpose of continuous integration

• Question 2:

  Which of the following tools would you expect to be the most useful to report defects found during exploratory testing sessions in Agile projects?

  A. Tools that generate data to populate an application's database
  B. Continuous integration and build distribution tools
  C. Application lifecycle management (ALM) and task management tools
  D. Tools that capture and log activities performed on an application during its use
  D. Tools that capture and log activities performed on an application during its use

  ---

  From CTFL-AT Syllabus v4.0, Section 3.1 Exploratory Testing: "Exploratory testing benefits from tools that record tester activity, allowing the tester to reproduce and document issues found during unscripted testing sessions."

  Option D is correct activity capture tools help testers log, replay, and report findings effectively in exploratory sessions.

  Option A is for test data preparation, not reporting.

  Option B is related to integration, not exploratory testing.

  Option C helps track tasks but lacks session capture features.

  References:

  CTFL-AT Syllabus v4.0, Section 3.1

  Learning Objective (K2) . Use appropriate tools during exploratory testing

• Question 3:

  Which of the following statements is FALSE regarding early and frequent feedback?

  A. Early feedback decreases the amount of time needed for system testing.
  B. Early feedback promotes early discovery and resolution of quality problems.
  C. Early feedback provides the Agile team with information on its productivity.
  D. Early feedback helps to deliver a product that better reflects what the customer wants.
  A. Early feedback decreases the amount of time needed for system testing.

  ---

  Early and frequent feedback is one of the core values of Agile development. It helps the Agile team to deliver features with the highest business value first, to discover and resolve quality problems as soon as possible, to provide information on the team's productivity and progress, and to ensure that the product meets the customer's expectations and needs. However, early feedback does not necessarily decrease the amount of time needed for system testing, as system testing is still an important activity in

  Agile projects to verify the integration and functionality of the whole system. Early feedback may reduce the number of defects found in system testing, but it does not eliminate the need for system testing.

  References:

  ISTQB Foundation Level Agile Tester Extension Syllabus,

• Question 4:

  Which tasks are typically performed by a tester on an Agile project?

  1) Implementing test strategy.

  2) Documenting business requirements.

  3) Measuring and reporting test coverage.

  4) Coaching development team in relevant aspects of testing.

  5) Executing test-driven development tests.

  A. 2, 5
  B. 2, 4, 5
  C. 1, 3, 4
  D. 1, 3
  C. 1, 3, 4

  ---

  A tester on an Agile project typically performs the following tasks:

  Implementing test strategy: A tester helps to define and implement the test strategy for the Agile project, which includes the test approach, test levels, test types, test techniques, test tools, test environment, test data, test metrics, and test documentation.

  Measuring and reporting test coverage: A tester measures and reports the test coverage of the product features and quality attributes, such as functionality, usability, performance, security, etc. Test coverage can be expressed in terms of test cases, test scenarios, test sessions, test conditions, test data, code, etc.

  Coaching development team in relevant aspects of testing: A tester coaches the development team in relevant aspects of testing, such as test design, test execution, test automation, test-driven development, behavior-driven development, exploratory testing, etc. A tester also helps the development team to improve their testing skills and practices.

  The following tasks are not typically performed by a tester on an Agile project:

  Documenting business requirements: Business requirements are usually documented by the product owner or the business analyst, not by the tester. The tester may review and provide feedback on the business requirements, but the tester is not responsible for documenting them.

  Executing test-driven development tests: Test-driven development tests are usually executed by the developers, not by the tester. The tester may assist the developers in creating and reviewing the test-driven development tests, but the tester is not responsible for executing them.

  Therefore, the correct answer is C, as it contains the tasks that are typically performed by a tester on an Agile project.

  References:

  ISTQB Foundation Level Agile Tester Extension Syllabus1, pages 14-15, 18-19, 22-23;

• Question 5:

  You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing. As an agile tester, which of the following actions should you take?

  A. Review the design of the problematic user story and improve it where possible.
  B. Create a bug report for each of your blocked tests.
  C. Work together with the developer, suggesting reasons why the tests are failing.
  D. Use the time to improve and automate existing test cases of other user stories.
  C. Work together with the developer, suggesting reasons why the tests are failing.

  ---

  As an agile tester, you should work together with the developer, suggesting reasons why the tests are failing. This is an example of the agile principle of collaboration and communication within the team, as well as the agile testing practice of early and frequent feedback. By working together with the developer, you can help to identify and resolve the root causes of the test failures, as well as share your testing knowledge and perspective. This can lead to faster and better quality delivery of the user story, as

  well as improved team relationships and trust.

  Option A is not a good action, because reviewing and improving the design of the user story is not the tester's responsibility, and it may not address the test failures.

  Option B is also not a good action, because creating bug reports for blocked tests is not an agile way of handling issues, and it may create unnecessary overhead and waste.

  Option D is not a good action, because it does not help to unblock the current user story, and it may distract you from the sprint goal and the team's focus.

  References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171;

• Question 6:

  Which of the following allows a developer to define accurate unit tests focused on business needs?

  A. Design-Driven Development
  B. Behavior-Driven Development
  C. Test-Driven Development
  D. Acceptance Test-Driven Development
  B. Behavior-Driven Development

  ---

  Behavior-Driven Development (BDD) is a software development approach that allows a developer to define accurate unit tests focused on business needs. BDD uses a common language that is understandable by both technical and non-technical stakeholders, such as Given-When-Then scenarios. BDD helps to align the development and testing activities with the customer expectations and business goals.

  References: ISTQB. Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2 ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2

• Question 7:

  Which of the following is the MOST likely reason to automate regression tests in Agile?

  A. To eliminate all manual testing
  B. To provide fast feedback during continuous integration
  C. To ensure testers focus only on exploratory testing
  D. To reduce development time by 50%
  B. To provide fast feedback during continuous integration

  ---

  CTFL-AT Section 4.3 emphasizes automation for rapid feedback in CI environments.

  Option A is unrealistic.

  Option C misrepresents testing balance.

  Option D is not an Agile objective.

  References:

  CTFL-AT Syllabus v4.0, Section 4.3

• Question 8:

  Which of the following statements describes a key advantage of continuous integration?

  A. It eliminates the need for testers
  B. It reduces integration issues by merging changes frequently
  C. It ensures all tests are manual
  D. It delays defect detection
  B. It reduces integration issues by merging changes frequently

  ---

  From CTFL-AT Section 4.2, CI reduces integration problems through frequent merges and automated verification.

  Option A is incorrect.

  Option C is the opposite of CI's goals.

  Option D contradicts early defect detection.

  References:

  CTFL-AT Syllabus v4.0, Section 4.2

• Question 9:

  Which ONE of the following statements BEST describes why whole-team testing is encouraged in Agile?

  A. It allows testers to avoid writing any test cases
  B. It ensures quality is a shared responsibility across all roles
  C. It enables the Product Owner to handle all defect reporting
  D. It reduces the need for technical collaboration
  B. It ensures quality is a shared responsibility across all roles

  ---

  Section 1.2 of CTFL-AT emphasizes collaborative, cross-functional teamwork and shared ownership of quality.

  Option B reflects this principle.

  Options A, C, and D contradict Agile values.

  References:

  CTFL-AT Syllabus v4.0, Section 1.2

• Question 10:

  Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

  A. Having at least once a day an automated build and test process that detects integration errors early and quickly.
  B. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
  C. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
  D. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
  C. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.

  ---

  knowledge and skills to ensure project success. The whole-team approach means that the business representatives, testers, and developers work together in every step of the development process, from planning to delivery. The whole-team approach aims to enhance communication and collaboration within the team, leverage the various skill sets of the team members, and make quality everyone's responsibility.

  Therefore, statement C is the most direct advantage of the whole-team approach, as it captures the essence of the principle and its benefits. The other statements are not directly related to the whole-team approach, or are incorrect.

  Statement A is about continuous integration, which is a practice of agile development that involves having at least once a day an automated build and test process that detects integration errors early and quickly. Continuous integration is not a direct consequence of the whole-team approach, although it may be facilitated by it.

  Statement B is about avoiding requirements misunderstandings, which may be a benefit of the whole-team approach, but not the most direct one. The whole-team approach does not only focus on requirements, but also on design, implementation, testing, and delivery. Moreover, avoiding requirements misunderstandings may also depend on other factors, such as the quality of the user stories, the use of acceptance criteria, and the feedback from the customers and users.

  Statement D is incorrect, as it contradicts the whole-team approach. The whole-team approach does not reduce the involvement of business representatives, but rather increases it. Business representatives are an integral part of the whole-team approach, as they provide the vision, the value, and the validation of the product. They collaborate with the testers and developers to define the features, prioritize the backlog, and verify the outcomes.

  References:

  ISTQB Foundation Level Agile Tester Syllabus, Section 1.2.1, page 9; What is Whole Team Approach in Agile Testing?, Section “What is Whole Team Approach?”; Continuous Integration, Section “What is Continuous Integration?”; Effective User Stories – 3C's and INVEST Guide, Section “The 3 C's (Card, Conversation, Confirmation) of User Stories.”