ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 1:

  You have been asked to execute an exploratory testing session on Park and Ride system. The test charter has been titled as Buy a bus ticket. As a result, a number of defects were reported, the titles of which are listed below. Which defect is out of scope for the given test charter?

  A. Price for a bus ticket was calculated incorrectly.
  B. Failed to buy a bus ticket after 18:00.
  C. Failed to buy a bus ticket when the network connection to the Central System is down.
  D. Payment for parking ticket is restricted to cash only (no credit card supported).
  D. Payment for parking ticket is restricted to cash only (no credit card supported).

  ---

  explanation:

  The test charter for the exploratory testing session is focused on buying a bus ticket, not a parking ticket. Therefore, any defect related to the payment for parking ticket is out of scope for the given test charter. The other defects are related to the functionality, usability, or reliability of buying a bus ticket, which are in scope for the test charter.

• Question 2:

  A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations.

  Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?

  1) A task to design the features planned for the next sprint.

  2) A task to run an acceptance test for a user story.

  3) A task to automate regression tests.

  4) A task to participate in training in preparation for the fourth sprint.

  5) A task to produce a daily progress report for the agile team members.

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

  ---

  explanation:

  According to the ISTQB Tester Foundation Level Agile Tester syllabus, an agile task board is a visual tool that displays the status of the work items in an agile sprint. The task board typically shows the user stories, tasks, and their progress from to do to done. The task board helps the agile team monitor and coordinate their work, and communicate with stakeholders. Therefore, the examples that represent activities that would likely be managed on an agile task board for the third sprint are those that are

  related to the user stories, tasks, and their progress in the current sprint.

  Option A is the correct answer, as it contains two examples of such activities: running an acceptance test for a user story and automating regression tests. These are both tasks that are part of the testing process in the current sprint, and their status can be tracked on the task board.

  Option B is not a correct answer, as it contains two examples of activities that are not related to the current sprint: designing the features planned for the next sprint and participating in training in preparation for the fourth sprint. These are both activities that are part of the planning or learning process for future sprints, and they are not managed on the task board.

  Option C is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: participating in training in preparation for the fourth sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the learning or reporting process, and they are not managed on the task board.

  Option D is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: designing the features planned for the next sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the planning or reporting process, and they are not managed on the task board.

  References:

  ISTQB Tester Foundation Level Agile Tester syllabus, Section 2.1.1, page 14; Section 2.1.2, page 15; Section 2.2.1, page 16; Section 2.2.2, page 17.

• Question 3:

  Which of the following describes a direct benefit of early and frequent feedback associated with the adoption of continuous integration?

  A. Detecting and isolating code quality problems early
  B. Reducing the need of conducting retrospectives
  C. Making quality everyone's responsibility
  D. Eliminating communication problems within the team
  A. Detecting and isolating code quality problems early

  ---

  explanation:

  From the CTFL-AT Syllabus v4.0, Section 4.2 Continuous Integration, it describes:

  “A major benefit of continuous integration is the ability to detect integration problems, code defects, and broken builds early, allowing for faster resolution.”

  And:

  “Continuous integration allows frequent builds and tests to be performed, helping to identify and isolate problems soon after they are introduced.”

  This directly confirms that Option A is the correct answer, highlighting the core value of continuous integration: early detection and isolation of issues.

  Option B is incorrect - retrospectives remain essential in Agile regardless of CI.

  Option C is an Agile principle, but not a direct benefit tied specifically to CI.

  Option D overstates the impact of CI - while CI may help communication, it does not eliminate communication problems by itself.

  References:

  CTFL-AT Syllabus v4.0, Section 4.2, Learning Objective (K2): Understand the benefits of continuous integration in Agile.

• Question 4:

  Consider an Agile team using a development practice with these steps:

  Write a failing test for a small piece of code Make the test pass by implementing minimal code Refactor the code Repeat the process with additional small functionality

  Which one of the following testing quadrants would the tests produced with this practice be part of?

  A. Q4 - Technology-facing tests that critique the product
  B. Q2 - Business-facing tests that support the team
  C. Q3 - Business-facing tests that critique the product
  D. Q1 - Technology-facing tests that support the team
  D. Q1 - Technology-facing tests that support the team

  ---

  explanation:

  From CTFL-AT Syllabus v4.0, Section 3.2 Test-Driven Development, and Section 3.4 Testing Quadrants:

  “TDD focuses on writing unit tests before code is implemented. These are technology-facing tests that support the team and are categorized under Q1.”

  Therefore, Option D is correct.

  Option A involves performance/security testing.

  Options B and C involve business-facing tests, not applicable to TDD.

  References:

  CTFL-AT Syllabus v4.0, Sections 3.2 and 3.4

  Learning Objective (K2) – Identify test types and quadrants.

• Question 5:

  You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

  A. Allocate independent testers to design exploratory tests using test charters in time boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5 hours.
  B. Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.
  C. Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.
  D. Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.
  D. Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.

  ---

  explanation:

  Exploratory testing is a testing approach that emphasizes learning, creativity, and adaptability. It involves simultaneous test design and test execution, where the tester uses heuristics, intuition, and experience to explore the system under test and discover new information. Exploratory testing can be performed in an Agile project to complement other testing activities, such as test-driven development, behavior-driven development, and acceptance test-driven development.

  The correct approach to adopt for exploratory testing in an Agile project is D, as it follows the best practices for exploratory testing:

  Ask experienced testers to prepare test charters for time-boxed sessions lasting no more than 2 hours:

  A test charter is a brief document that describes the scope, objective, and strategy of an exploratory testing session. A test charter helps guide the tester's exploration and document the results. A time box is a fixed period allocated for an exploratory session. It helps keep focus and limits scope. A time box should not be too long, as it may reduce concentration and creativity. A recommended duration is between 45 minutes and 2 hours.

  Tests should be designed and executed within each session using heuristics, creativity, and intuition:

  Exploratory testing is iterative and interactive. The tester designs and executes tests based on observations and feedback from the system. The tester uses heuristics (rules of thumb that help simplify complex problems), along with creativity and intuition, to generate test ideas and make informed decisions.

  The incorrect approaches to adopt for exploratory testing in an Agile project are A, B, and C, as they violate the principles and practices of exploratory testing:

  Option A: Allocate independent testers to design exploratory tests using test charters in time-boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5 hours:

  This approach is incorrect because it separates test design from test execution, which contradicts the core of exploratory testing. It also uses excessively long time boxes, which can harm focus and creativity. Additionally, it reduces collaboration within the Agile team by isolating testers from developers and stakeholders.

  Option B: Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools:

  This approach is incorrect because it does not use test charters, which are essential for guiding and documenting exploratory testing sessions. It also overlooks heuristics, creativity, and intuition as structured methods for generating test ideas. It suggests that exploratory testing is random and unstructured, which is a misconception—exploratory testing is disciplined and systematic.

  Option C: Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time-boxed session for the sprint:

  This approach is incorrect because it separates test design from execution. It also uses testers who were not part of the sprint, which may limit their understanding of the product and user needs. It does not use test charters and does not rely on heuristics, creativity, or intuition, all of which are essential to exploratory testing.

• Question 6:

  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

  ---

  explanation:

  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 7:

  Which of the following statements is true within an Agile team?

  A. Unlike traditional projects, testers are not asked to measure and report test coverage, and to report defects
  B. When adopting test-driven development, testers write all the tests while developers write all the code to make these tests pass
  C. Each team member plays a role in performing test-related tasks but only testers are responsible for product quality
  D. Testers may have difficulty keeping pace with the incoming changes in time-boxed iterations
  D. Testers may have difficulty keeping pace with the incoming changes in time-boxed iterations

  ---

  explanation:

  From CTFL-AT Syllabus v4.0, Section 2.4 and 2.5:

  "Due to frequent changes and short iterations, testers must be flexible and responsive. However, keeping up with pace can be a challenge."

  Thus, Option D is correct testers may struggle with rapid changes and short feedback loops, which is a known challenge in Agile.

  Option A is false, testers still measure coverage and report defects.

  Option B misrepresents TDD developers typically write the unit tests in TDD.

  Option C is incorrect quality is a shared responsibility in Agile.

  References:

  CTFL-AT Syllabus v4.0, Sections 2.4 and 2.5 Learning Objective (K2) . Understand tester challenges in Agile environments

• Question 8:

  Which two of the following statements are CORRECT with regards to test automation on agile projects?

  1) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

  2) It would be very difficult to ensure high quality in an agile project without test automation.

  3) Automated acceptance tests are run regularly as part of the continuous integration full system build.

  4) Automated regression suites are only run for the final release of code.

  5) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

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

  ---

  explanation:

  Test automation is essential for agile projects, as it enables fast and frequent feedback on the quality of the product. Without test automation, it would be very difficult to ensure high quality in an agile project, as manual testing would be too slow and costly to keep up with the pace of development. Automated acceptance tests are one of the key types of test automation on agile projects, as they verify that the user stories are implemented correctly and that the product meets the customer's expectations. Automated acceptance tests are run regularly as part of the continuous integration full system build, and the results provide feedback on the overall product quality. Therefore, statements 2 and 5 are correct with regards to test automation on agile projects.

  References:

  1: ISTQB. Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation;

  2: ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation

• Question 9:

  User Story: As a user I want to be able to calculate tax percentage based on amount of income. What is the best black box test design technique for verifying the accuracy of this user story?

  A. Statement testing - test all statements in income calculation.
  B. User story testing - test that the user can enter an income amount and get a result.
  C. State transition testing - test all states of income entry.
  D. Equivalence partitioning - test with low, medium and high income.
  D. Equivalence partitioning - test with low, medium and high income.

  ---

  explanation:

  The best black-box test design technique for verifying the accuracy of this user story is equivalence partitioning. Equivalence partitioning is a technique that divides the input domain of a system into classes or groups that are expected to behave similarly. By testing one value from each class, the tester can reduce the number of test cases while still achieving good coverage.

  In this case, the input domain of the system is the amount of income, which can be divided into classes based on the tax percentage applied to different income ranges. For example, if the tax percentage is 10% for income below 10,000, 20% for income between 10,000 and 20,000, and 30% for income above 20,000, then the equivalence classes are: low income (<10,000), medium income (10,000–20,000), and high income (>20,000).

  By testing one value from each class, such as 5,000, 15,000, and 25,000, the tester can verify that the system calculates the correct tax percentage for each income range. This technique is more efficient and effective than testing all possible values of income, testing only one value of income, testing the states of income entry, or testing the statements in income calculation.

• Question 10:

  Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

  1) User access for all roles has been validated.

  2) A static analysis tool has been executed for all code.

  3) 100% of the existing regression test suite has passed.

  4) System is responding in less than 3 seconds, 90% of the time.

  5) A new version of internet Explorer has been included.

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

  ---

  explanation:

  The acceptance criteria for a sprint are the conditions that must be met for the user stories to be considered done and deliver value to the customer. The acceptance criteria should be specific, measurable, achievable, relevant, and testable. In this case, the plan for the sprint is to increase the performance of the system, so the acceptance criteria should reflect that goal.

  Therefore, the acceptance criteria that would be expected for Sprint 5 are:

  100% of the existing regression test suite has passed.

  This criterion ensures that the system has not introduced any new defects or broken any existing functionality while improving performance.

  System is responding in less than 3 seconds, 90% of the time.

  This criterion defines a clear and quantifiable performance target that can be verified by testing.

  The other options are not relevant or appropriate acceptance criteria for Sprint 5:

  User access for all roles has been validated.

  This criterion is not related to the performance of the system, but rather to the security or functionality of the system. It might be an acceptance criterion for a different sprint or user story, but not for Sprint 5.

  A static analysis tool has been executed for all code.

  This criterion is not a customer-facing requirement and does not directly reflect performance improvements.