ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 151:

  An alphanumeric password must be between 4 and 7 characters long and must contain at least one numeric character, one capital (uppercase) letter and one lowercase letter of the alphabet.

  Which one of the following sets of test cases represents the correct outcome of a two-value boundary value analysis applied to the password length? (Note: test cases are separated by a semicolon)

  A. 1xA;aB11;Pq1ZZab;7iDD0a1x
  B. aB11;99rSp:5NnN10;7iDD0a1x
  C. 1xB: aB11: 99rSp: 5NnN10; 4NnN10T; 44ghWn19
  D. 1RhT;rSp53;3N3e10;8sBdby
  D. 1RhT;rSp53;3N3e10;8sBdby

  ---

  Explanation

  The correct outcome of a two-value boundary value analysis applied to the password length is the set of test cases represented by option

  D. Boundary value analysis is a test design technique that focuses on the values at the boundaries of

  an equivalence partition, such as the minimum and maximum values, or the values just above and below the boundaries. A two-value boundary value analysis uses two values for each boundary, one representing the valid value and one

  representing the invalid value. For example, if the valid range of values is from 4 to 7, then the two values for the lower boundary are 3 and 4, and the two values for the upper boundary are 7 and 8. The test cases in option D use these values

  for the password length, while also satisfying the other requirements of the password, such as containing at least one numeric character, one capital letter, and one lowercase letter. The test cases in option D are:

  1RhT: a 4-character password that is valid

  rSp53: a 5-character password that is valid

  3N3e10: a 6-character password that is valid

  8sBdby: an 8-character password that is invalid

  The test cases in the other options are incorrect, because they either use values that are not at the boundaries of the password length, or they do not meet the other requirements of the password. For example, the test cases in option A are:

  1xA: a 3-character password that is invalid, but it does not contain a capital letter

  aB11: a 4-character password that is valid

  Pq1ZZab: a 7-character password that is valid

  7iDD0a1x: an 8-character password that is invalid

  References:

  ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

  ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.1, Black-box Test Design Techniques1

  ISTQB Glossary of Testing Terms v4.0, Boundary Value Analysis, Equivalence Partition2

• Question 152:

  Which of the following statements is true?

  A. In Agile software development, work product documentation tends to be lightweight and manual tests tend to be often unscripted as they are often produced using experience-based test techniques
  B. Sequential development models impose the use of systematic test techniques and do not allow the use of experience-based test techniques
  C. In Agile software development, the first iterations are exclusively dedicated to testing activities, as testing will be used to drive development, which will be performed in the subsequent iterations
  D. Both in Agile software development and in sequential development models, such as the V-model, test levels tend to overlap since they do not usually have defined entry and exit criteria
  A. In Agile software development, work product documentation tends to be lightweight and manual tests tend to be often unscripted as they are often produced using experience-based test techniques

  ---

  Explanation

  This answer is correct because in Agile software development, work product documentation, such as user stories, acceptance criteria, or test cases, tends to be lightweight and concise, as the focus is on working software and frequent communication rather than comprehensive documentation. Manual tests tend to be often unscripted, as they are often produced using experience-based test techniques, such as error guessing or exploratory testing, which rely on the tester's skills, knowledge, and creativity to find defects and provide feedback.

  References: ISTQB Foundation Level Syllabus v4.0, Section 3.1.1.2, Section 3.2.1.2

• Question 153:

  Consider the following user story about the authentication functionality of an e-commerce website:

  "As a logged-in user, I want to change my current password with a new one, so that I can make my account safer".

  The following are some of the acceptance criteria defined for the user story:

  [a] After the logged-in user has successfully changed his password, an email confirming the change must be sent to him

  [b] To successfully change the password, the logged-in user must enter the current password, enter a new valid password, and finally confirm by pressing the 'Change Password' button [c] To be valid, the new password entered by the logged-in user is not only required to meet the criteria related to the length and type of characters, but must also be different form the last 5 passwords of that user [d] A dedicated error message must be presented to the logged-in user when he enters a wrong current password

  [e] A dedicated error message must be presented to the logged-in user when he enters the correct current password, but enters an invalid password

  Based only on the given information, which of the following ATDD tests is most likely to be written first?

  A. The logged-in user enters a wrong current password and views the dedicated error message
  B. The logged-in user enters the correct current password, enters a valid new password (different from the last 5 passwords), presses the Change Password' button, and finally receives the e-mail confirming that the password has been successfully changed
  C. The logged-in user enters the correct current password, enters an invalid password, and finally views the dedicated error
  D. The logged-in user submits a purchase order containing ten items, selects to pay with a Visa credit card, enters credit card information of a valid card, presses the 'Confirm' button, and finally views the dedicated message confirming that the purchase has been successful
  B. The logged-in user enters the correct current password, enters a valid new password (different from the last 5 passwords), presses the Change Password' button, and finally receives the e-mail confirming that the password has been successfully changed

  ---

  Explanation

  ATDD stands for Acceptance Test-Driven Development, which is a collaborative approach to software development and testing, in which the acceptance criteria of a user story are defined and automated as executable tests before the

  implementation of the software system. ATDD tests are usually written in a Given- When-Then format, which describes the preconditions, the actions, and the expected outcomes of a test scenario. ATDD tests are intended to verify that the

  software system meets the expectations and the needs of the users and the stakeholders, as well as to provide feedback and guidance for the developers and the testers. Based on the given information, the ATDD test that is most likely to be

  written first is the one that corresponds to option B, which is:

  Given the logged-in user is on the Change Password page When the user enters the correct current password, enters a valid new password (different from the last 5 passwords), and presses the Change Password button Then the user

  receives an email confirming that the password has been successfully changed

  This ATDD test is most likely to be written first, because it covers the main functionality and the happy path of the user story, as well as the most important acceptance criterion [a]. It also verifies that the user can change the password with a

  valid new password that meets the criteria related to the length, the type of characters, and the history of the passwords, as specified in the acceptance criterion [c]. The other options are not likely to be written first, because they either cover

  less critical or less frequent scenarios, such as entering a wrong current password [d] or an invalid new password [e], or they are not related to the user story or the acceptance criteria at all, such as submitting a purchase order [d].

  References:

  ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

  ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.3.1, Testing in Software Development Lifecycles1

  ISTQB Glossary of Testing Terms v4.0, Acceptance Test-Driven Development, User Story, Acceptance Criterion, Given-When-Then2

• Question 154:

  In which phase of a formal review are entry criteria checked?

  A. Review planning
  B. Kick-off meeting
  C. Review preparation
  D. Review initiation
  A. Review planning

  ---

  Explanation

  Entry criteria are verified before a review formally begins.

• Question 155:

  The following sentences refer to the 'Standard for Software Test Documentation' specification (IEEE 829). Which sentence is correct?

  A. Any deviation from this standard should be approved by management, marketing and development
  B. Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization
  C. The key to high quality test documentation regimes is strict adherence to this standard
  D. This test plan outline is relevant for military projects. For consumer market projects there is a different specification with fewer items.
  B. Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization

  ---

  Explanation

  The IEEE 829 standard is a widely used specification for test documentation, but it is not mandatory or universal. Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization. The standard does not require any approval from management, marketing or development for any deviation, nor does it depend on the type of project (military or consumer market). The standard also does not guarantee high quality test documentation regimes, as it only provides a general outline and format, not the actual content or quality criteria. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 16.

• Question 156:

  Which ONE of the following elements is TYPICALLY part of a test plan ?

  A. The budget and schedule for the test project.
  B. A detailed analysis of the defects found and their causes.
  C. A detailed report on the test results after the test project is completed.
  D. A list of test logs from the test execution.
  A. The budget and schedule for the test project.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  A test plan is a management document that outlines the scope, objectives, schedule, resources, and risks of the testing process. The budget and schedule (A) are essential components as they help plan resources and timeline constraints.

  (B)

  is incorrect because defect analysis is part of the test summary report , not the test plan.

  (C)

  is incorrect because final reports summarize execution , while the test plan is created before testing starts .

  (D)

  is incorrect because test logs are execution artifacts rather than planning elements.

  A test plan guides testing activities and ensures alignment with project objectives.

  ISTQB CTFL v4.0 Syllabus, Section 5.1.1 ?Test Planning

• Question 157:

  The following incident report that was generated during test of a web application.

  What would you suggest as the most important report improvement?

  1.Defect detected date: 15 8.2010

  2.Defect detected by: Joe Smith

  3.Test level System test

  4.Test case: Area 5/TC 98

  5.Build version: 2011-16.2

  Defect description After having filled out all required fields in screen 1, t click ENTER to continue to screen 2 Nothing happens, no system response at all.

  A. Add information about which web browser was used
  B. Add information about which developer should fix the bug
  C. Add the time stamp when the incident happened
  D. Add an impact analysis
  A. Add information about which web browser was used

  ---

  Explanation

  The most important report improvement for the given incident report would be to add information about which web browser was used when the defect was detected. This information is relevant for reproducing and debugging the defect, as different web browsers may have different behaviors or compatibility issues with the web application. The other options are less important or irrelevant for the incident report. The developer who should fix the bug can be assigned by the project manager or the defect tracking system, not by the tester who reports the defect. The time stamp when the incident happened is not very useful, as it does not indicate the cause or the frequency of the defect. The impact analysis is not part of the incident report, but rather of the risk assessment or prioritization process. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 140.

• Question 158:

  Which of the following BEST defines risk level?

  A. Risk level is determined by calculating the absolute value of the sum of all potential issues that may occur on the project
  B. Risk level is calculated by adding the probabilities of all planned risks to a project
  C. Risk level is calculated by dividing the sum of all known risks by the sum of all unknown risks
  D. Risk level is determined by the likelihood of an event happening and the impact or harm from that event
  D. Risk level is determined by the likelihood of an event happening and the impact or harm from that event

  ---

  Explanation

  Risk level is determined by the combination of two factors: the likelihood of an event occurring and the impact or harm that could result from that event. This approach allows risks to be prioritized based on their potential effect on the project or

  system. The likelihood represents the probability of the risk event occurring, while the impact represents the severity of the consequences if the event does happen. This concept is fundamental in risk-based testing and helps guide decision-

  making during the testing process.

  References:

  ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 1.4.1.

• Question 159:

  Which two of the following statements describe the advantages provided by good traceability between the test basis and test work products?

  Which two of the following statements describe the advantages provided by good traceability between the test basis and test work products?

  I- Analyzing the impact of changes. ii- A measure of code quality. iii- Accurate test estimation. iv- Making testing auditable.

  Select the correct answer:

  A. i and ii
  B. i and iv
  C. i and iii
  D. ii and iii
  B. i and iv

  ---

  Explanation

  Good traceability between the test basis and test work products provides several advantages: i. Analyzing the impact of changes: Traceability allows for easy identification of which parts of the test work products will be affected by changes in

  the requirements or design, facilitating impact analysis. iv. Making testing auditable:

  Traceability ensures that there is a clear connection between the requirements and the test cases, which makes the testing process auditable and provides evidence that all requirements have been tested.

• Question 160:

  Which of the following statements about how different types of test tools support testers is true?

  A. The support offered by a test data preparation tool is often leveraged by testers to run automated regression test suites
  B. The support offered by a performance testing tool is often leveraged by testers to run load tests
  C. The support offered by a bug prediction tool is often used by testers to track the bugs they found
  D. The support offered by a continuous integration tool is often leveraged by testers to automatically generate test cases from a model
  B. The support offered by a performance testing tool is often leveraged by testers to run load tests

  ---

  Explanation

  The support offered by a performance testing tool is often leveraged by testers to run load tests, which are tests that simulate a large number of concurrent users or transactions on the system under test, in order to measure its performance,

  reliability, and scalability. Performance testing tools can help testers to generate realistic workloads, monitor system behavior, collect and analyze performance metrics, and identify performance bottlenecks. The other statements are false,

  because:

  A test data preparation tool is a tool that helps testers to create, manage, and manipulate test data, which are the inputs and outputs of test cases. Test data preparation tools are not directly related to running automated regression test suites,

  which are test suites that verify that the system still works as expected after changes or modifications. Regression test suites are usually executed by test execution tools, which are tools that can automatically run test cases and compare

  actual results with expected results.

  A bug prediction tool is a tool that uses machine learning or statistical techniques to predict the likelihood of defects in a software system, based on various factors such as code complexity, code churn, code coverage, code smells, etc. Bug

  prediction tools are not used by testers to track the bugs they found, which are the actual defects that have been detected and reported during testing. Bugs are usually tracked by defect management tools, which are tools that help testers to

  record, monitor, analyze, and resolve defects.

  A continuous integration tool is a tool that enables the integration of code changes from multiple developers into a shared repository, and the execution of automated builds and tests, in order to ensure the quality and consistency of the

  software system. Continuous integration tools are not used by testers to automatically generate test cases from a model, which are test cases that are derived from a representation of the system under test, such as a state diagram, a

  decision table, a use case, etc. Test cases can be automatically generated by test design tools, which are tools that support the implementation and maintenance of test cases, based on test design specifications or test models.

  References:

  ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

  ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.4.1, Types of Test Tools

  ISTQB Glossary of Testing Terms v4.0, Performance Testing Tool, Test Data Preparation Tool, Bug Prediction Tool, Continuous Integration Tool, Test Execution Tool, Defect Management Tool, Test Design Tool