ISTQB-CTFL Tested & Approved Foundation Level Study Materials
Validate your Skills with Updated Foundation Level Exam Questions & Answers and Test Engine
NEW QUESTION # 14
Which of the following is a correct reason to apply test automation?
- A. When it is easy to automate
- B. When there are a lot of repetitive testing tasks
- C. When it is cheap to buy test automation tools
- D. When a new test automation tool is launched
Answer: B
Explanation:
A correct reason to apply test automation is when there are a lot of repetitive testing tasks. Test automation is the use of software tools or scripts to perform or support testing activities, such as test case execution, test result comparison, test data generation, etc. Test automation can be beneficial when there are a lot of repetitive testing tasks that need to be performed frequently or consistently, such as regression testing, performance testing, load testing, etc. Test automation can help to save time and effort, increase reliability and accuracy, and improve coverage and efficiency of testing. The other options are not correct reasons to apply test automation. When a new test automation tool is launched is not a reason to apply test automation, but rather a factor for choosing a test automation tool. When it is easy to automate is not a reason to apply test automation, but rather a factor for evaluating the feasibility of test automation. When it is cheap to buy test automation tools is not a reason to apply test automation, but rather a factor for estimating the cost and benefit of test automation. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 10.
NEW QUESTION # 15
A mid-size software product development company has analyzed data related to defects detected in its product and found out that detects fixed in earlier builds are getting re-opened after a few months.
The company management now seeks your advice in order to reverse this trend and prevent re-opening of defects fixed earlier.
What would be your FIRST recommendation to the company?
- A. Analyze the product modules containing maximum defects, and get them thoroughly tested and defects fixed as a one-time activity
- B. If required, tram the teams responsible for development and testing of the modules containing maximum number of defects, and if this does not help, replace them with more knowledgeable people
- C. Automate existing test suits so that lesser time is spent on execution of each test, and more tests can be executed m the available time thus leading to a lower probability of defects slipping by
- D. Verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build
Answer: D
Explanation:
Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes. Regression testing can help prevent re-opening of defects fixed earlier by ensuring that they do not cause any new failures or side effects. The first recommendation to the company is to verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build. This can help improve the coverage and effectiveness of regression testing and detect any regression defects as soon as possible. Automating existing test suites may also help reduce the time and effort required for regression testing, but this is not the first recommendation, as automation may not be feasible or cost-effective for all test cases. Analyzing the product modules containing maximum defects and getting them thoroughly tested and defects fixed as a one-time activity may also help reduce the defect density and improve the quality of those modules, but this is not the first recommendation, as it does not address the root cause of re-opening defects fixed earlier. Training or replacing the teams responsible for development and testing of the modules containing maximum number of defects may also help improve their skills or performance, but this is not the first recommendation, as it may not be necessary or appropriate for all teams. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 19; Chapter 4, page 45.
NEW QUESTION # 16
Which of the following does MOT describe a reason why testing is necessary?
- A. The customer decided that 100% branch coverage shall be achieved
- B. The acquisition of test automation tools was based on the assumption that it will be used m all projects
- C. The risks associated with delivering the system are far higher than the cost of testing
- D. For avionics and pharmaceutical systems software testing is mandated by standards
Answer: B
Explanation:
Testing is necessary for various reasons, such as:
To detect defects and failures that may affect the quality, performance, reliability or security of a software product or system To verify that a software product or system meets its specified requirements, expectations and standards To validate that a software product or system fulfills its intended purpose and satisfies its stakeholders' needs To provide information and feedback about the status and risks of a software product or system To comply with regulations or contractual obligations that mandate testing for certain types of software products or systems The following statements describe some reasons why testing is necessary:
A) The customer decided that 100% branch coverage shall be achieved. This is a reason why testing is necessary, as it reflects a contractual obligation or a quality standard that requires testing to measure and achieve a certain level of code coverage.
C) For avionics and pharmaceutical systems software testing is mandated by standards. This is a reason why testing is necessary, as it reflects a regulation or a compliance requirement that mandates testing for certain types of software products or systems that have high safety or security risks.
D) The risks associated with delivering the system are far higher than the cost of testing. This is a reason why testing is necessary, as it reflects a risk-based approach that considers testing as an investment to reduce the probability and impact of potential failures or defects. The following statement does not describe a reason why testing is necessary:
B) The acquisition of test automation tools was based on the assumption that it will be used m all projects. This is not a reason why testing is necessary, as it reflects a business decision or a resource allocation that does not justify the need or purpose of testing. Test automation tools are not always suitable or beneficial for all projects, and testing can be performed with or without test automation tools. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 1, page 5-6.
NEW QUESTION # 17
During system testing phase of a word processor, a tester finds that on opening a file from a particular set of files, which are part of a critical workflow, the word processor crashes. Which of the following is the next step the tester should take poor to recording the deviation?
- A. Try to recreate the incident before reporting
- B. Send an email to the developer and not report the bug
- C. Report the incident as is without any further action
- D. Try to identify the code fragment causing the problem
Answer: A
Explanation:
An incident is any event that occurs during testing that requires investigation. An incident report is a document that records the details of an incident. The next step the tester should take prior to recording the deviation is to try to recreate the incident before reporting. This can help confirm that the incident is reproducible and not caused by a random or external factor. This can also help gather more information about the incident, such as the steps to reproduce it, the expected and actual results, the severity and priority of the incident, or any screenshots or logs that can illustrate the incident. Trying to identify the code fragment causing the problem is not the next step the tester should take prior to recording the deviation, as this is a debugging activity that is usually performed by developers after receiving the incident report. Sending an email to the developer and not reporting the bug is not the next step the tester should take prior to recording the deviation, as this is an informal and unstructured way of communicating incidents that can lead to confusion, inconsistency or loss of information. Reporting the incident as is without any further action is not the next step the tester should take prior to recording the deviation, as this can result in incomplete or inaccurate incident reports that can hamper the investigation and resolution of incidents. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 32-33.
NEW QUESTION # 18
Consider the following statements about risk-based testing.
I) Risk-based testing has the objective to reduce the level of protect risks.
II) Tests should be prioritized to find tie critical detects as early as possible.
III) Non-testing activities may also help to reduce risk
IV) Risks have to be reassessed on a regular basis.
V) The project stakeholders can give useful input to determine the risks
- A. II, Ill and V are true. 1 ants Iv are false.
- B. I, II and IV are true. III and V are false.
- C. II, III IV and V are correct. I is false.
- D. I III IV and V are true. II is false.
Answer: C
Explanation:
The following statements about risk-based testing are correct:
II) Tests should be prioritized to find tie critical detects as early as possible. Risk-based testing involves prioritizing tests based on risk level, which reflects both the likelihood and impact of defects or failures. Tests with higher risk level should be executed earlier than tests with lower risk level, in order to find and fix critical defects as soon as possible.
III) Non-testing activities may also help to reduce risk. Risk-based testing does not only involve testing activities, but also other activities that can help mitigate risks, such as reviews, inspections, audits, simulations or prototyping.
NEW QUESTION # 19
Which ONE of the following statements about acceptance testing is NOT correct?
- A. Testing of disaster recovery and backup/restore is usually NOT part of acceptance testing.
- B. The main goal of acceptance testing is to build confidence in the system, not find defects.
- C. Acceptance testing is the last level of testing performed prior to system release.
- D. The customers or system users are often responsible for the acceptance testing.
Answer: A
Explanation:
Acceptance testing is a level of testing performed to verify that a software product meets the agreed acceptance criteria and is acceptable for delivery. Acceptance testing is often performed by the customers or system users, who are the main stakeholders of the software product. The main goal of acceptance testing is to build confidence in the system, not find defects, as defects should have been detected and fixed in earlier levels of testing. Acceptance testing is the last level of testing performed prior to system release, unless there are any changes or fixes that require re-testing. Testing of disaster recovery and backup/restore is usually part of acceptance testing, as these are important aspects of system reliability and security that affect the customer satisfaction and trust. Therefore, statement A is not correct, while statements B, C and D are correct. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 2, page 20-21.
NEW QUESTION # 20
Which of the following statements is CORRECT?
- A. Test cases describe items or events to test that are derived from the test basis during the test analysis activity
- B. Test cases are sequences of actions for test execution specified during the test implementation activity D. Test cases are derived during the test design activity to cover test objectives or test conditions
- C. Test cases are made up of input values, expected results and actual results developed to cover test objectives
Answer: B
Explanation:
A test case is a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition. A test case is a sequence of actions for test execution that can be followed by a tester or a test automation tool. A test case is specified during the test implementation activity, which is the activity that prepares the testware needed for test execution. A test case does not include actual results, as these are obtained during test execution and compared with the expected results. A test case does not describe items or events to test, as these are derived from the test basis during the test analysis activity. A test case is not derived during the test design activity, as this is the activity that specifies the test conditions or objectives that need to be tested. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 23-24; Chapter 4, page 34.
NEW QUESTION # 21
Why should you choose a test technique?
- A. Because this way you cover the full scope of the product's functionality
- B. Because choosing a test technique is a common practice in software testing
- C. Because you need to match the way you test to the content of the product under test
- D. Because of the time constraints that usually accompany a test project
Answer: C
Explanation:
You should choose a test technique because you need to match the way you test to the content of the product under test. A test technique is a method or process for deriving and selecting test cases based on some criteria or rules. Different test techniques are suitable for different types of software products, depending on their characteristics, functionalities, requirements, specifications, risks, etc. Choosing a test technique helps to ensure that the test cases are relevant, effective, and efficient for the product under test. The other options are not correct reasons to choose a test technique. Time constraints are not a factor for choosing a test technique, but rather for prioritizing or optimizing testing activities. Covering the full scope of the product's functionality is not a guarantee of choosing a test technique, but rather a goal of testing. Choosing a test technique is not a common practice in software testing, but rather a professional skill and responsibility. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 31.
NEW QUESTION # 22
A system has valid input numbers ranging between 1000 and 99999 (both inclusive). Which of the following inputs are a result of designing tests for all valid equivalence classes and their boundaries?
- A. 1000,50000,99999
- B. 999.1000.23232.99999.100000
- C. 999.1000.50000.100000.100001
- D. 999.100000
Answer: C
Explanation:
A correct list of boundary values for the P input should include the minimum and maximum values of the valid range (15 and 350), as well as the values just below and above the boundaries (14 and 351). Boundary value analysis is a test design technique that involves testing the values at or near the boundaries of an input domain or output range, as these values are more likely to cause errors than values in the middle. Option B satisfies this condition, as it has all four boundary values (14, 15, 350, 351). Option A has two values from the same equivalence class (1000 and 99999), option C has two values outside the range (999 and 100000), and option D has no boundary values at all. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 34.
NEW QUESTION # 23
What is 'Component Testing'?
- A. A test level
- B. Integration Testing
- C. Experience-based testing
- D. Functional testing
Answer: A
Explanation:
Component testing is a test level. A test level is a group of test activities that are organized and managed together based on some common characteristics or objectives. A test level can be defined based on various factors, such as the scope and target of testing, the phase and model of development, the stakeholders and roles involved in testing, etc. Component testing (also known as unit testing or module testing) is a test level that focuses on verifying the functionality and quality of individual software components (such as modules, classes, functions, methods, etc.). Component testing can be performed by developers or testers using various techniques and tools depending on the type and complexity of the components. The other options are not test levels. Integration testing is another test level that focuses on verifying the functionality and quality of groups of software components that interact with each other or with external systems. Functional testing is a type of black-box dynamic testing that verifies that the system under test performs its intended functions according to its requirements or specifications. Experience-based testing is a category of test design techniques that rely on the tester's knowledge and intuition to derive and select test cases based on their experience with similar systems, technologies, domains, risks, etc. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 19.
NEW QUESTION # 24
Which of the following statements about re-testing and regression testing are TRUE?
I Re-testing should be performed after a defect is fixed.
II Regression testing should always be performed after a defect is fixed.
III Re-testing and regression testing may be performed at any test level.
IV Regression testing may include functional, non-functional and structural testing.
V Re-testing should be included in the debugging activity.
- A. II. IV, V
- B. II, v
- C. I, III. Iv
- D. I, Ill
Answer: C
Explanation:
The following statements about re-testing and regression testing are true:
I) Re-testing should be performed after a defect is fixed. Re-testing is a type of testing that verifies that a defect has been successfully resolved by executing a test case that previously failed due to that defect. Re-testing should be performed after a defect is fixed and delivered to ensure that it does not cause any new failures or side effects.
III) Re-testing and regression testing may be performed at any test level. Re-testing and regression testing are not limited to a specific test level, but can be applied at any level depending on the context and objectives. For example, re-testing and regression testing can be performed at unit level, integration level, system level or acceptance level.
IV) Regression testing may include functional, non-functional and structural testing. Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes. Regression testing may include various types of testing depending on the scope and purpose of the changes. For example, regression testing may include functional testing to check if the software meets its requirements, non-functional testing to check if the software meets its quality attributes, or structural testing to check if the software meets its design or code standards. The following statement about re-testing and regression testing is false:
II) Regression testing should always be performed after a defect is fixed. Regression testing is not always necessary after a defect is fixed, as some defects may have a low impact or low likelihood of affecting other parts of the software. Regression testing should be performed after a defect is fixed only if there is a risk of introducing new defects or causing existing defects due to the changes made to fix the defect. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 2, page 19; Chapter 4, page 45.
NEW QUESTION # 25
Which sequence of state transition stated in the answer choices is correct in accordance with the following figure depicting me life-cycle of a defect?
- A. S0->S1->S2->S3->S5^>S1
- B. S0->S1->S2->S3->S4
- C. S0->S1->S2->S3->S5->S1->S2->S3
- D. S0->S1->S2->S3->S5->S3->S4
Answer: C
Explanation:
The figure depicts the life-cycle of a defect using state transition testing. State transition testing is a technique that models how a system transitions from one state to another depending on events or conditions. The figure shows six states (S0 to S5) and seven transitions (T0 to T6). The correct sequence of state transitions that follows the figure is S0->S1->S2->S3->S5->S1->S2->S3. This sequence represents the following scenario:
S0: The defect is not yet detected (initial state).
T0: The defect is detected by testing (event).
S1: The defect is reported and registered (state).
T1: The defect is assigned to a developer for fixing (event).
S2: The defect is being fixed by the developer (state).
T2: The developer fixes the defect and delivers a new version (event).
S3: The defect is verified by testing (state).
T5: The testing fails to confirm that the defect is fixed (event).
S5: The defect is rejected by testing (state).
T6: The defect is reassigned to a developer for fixing (event).
S1: The defect is reported and registered (state).
T1: The defect is assigned to a developer for fixing (event).
S2: The defect is being fixed by the developer (state).
T2: The developer fixes the defect and delivers a new version (event).
S3: The defect is verified by testing (state). The other sequences are incorrect, as they do not follow the transitions shown in the figure. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 4, page 40-41.
NEW QUESTION # 26
Which of the following is correct with regards to debugging?
- A. Debugging is intended to find as many defects as possible in the code
- B. Debugging identifies the cause of a failure
- C. Debugging is considered part of the testing activities
- D. Debugging is often performed by test engineers
Answer: B
Explanation:
Debugging is the process of finding, analyzing and removing the causes of failures in software. Debugging is not considered part of testing, but rather a development activity that can involve testing. Debugging is not intended to find as many defects as possible, but rather to fix the specific failure that was observed. Debugging is usually performed by developers, not by test engineers. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 1, page 6.
NEW QUESTION # 27
In what way do Configuration Management effects testing?
- A. There is very little influence of configuration management practices on the test project.
- B. Proper configuration management ensures that testers can uniquely identity the tested item
- C. Configuration management is important for developers, not for testers
- D. Without proper configuration management, test planning cannot proceed.
Answer: B
Explanation:
Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle. Configuration management affects testing in various ways, such as:
Proper configuration management ensures that testers can uniquely identify the tested item, which can help traceability, reproducibility and accountability.
Proper configuration management ensures that testers have access to consistent versions of software components and testware, which can help reliability, compatibility and efficiency.
Proper configuration management ensures that testers can track changes and defects in software components and testware, which can help verification, validation and reporting.
Proper configuration management ensures that testers can control the configuration of the test environment, which can help stability, security and performance. Configuration management is not a prerequisite for test planning, as test planning can proceed without configuration management, although it may be less effective or accurate. Configuration management is not important for developers only, but for testers as well, as it affects the quality and consistency of the testing process and products. Configuration management has a significant influence on the test project, as it affects various aspects of testing, such as traceability, reproducibility, reliability, compatibility, efficiency, verification, validation, reporting, stability, security and performance. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 6, page 60-61.
NEW QUESTION # 28
Which of the following tools is most likely to detect defects in functions or methods in source code?
- A. configuration management tool
- B. monitoring tool
- C. unit test framework tool
- D. test design tool
Answer: C
Explanation:
A unit test framework tool is a tool that supports the creation, execution, and reporting of unit tests, which are tests that verify the functionality and quality of individual software components (such as functions or methods) in source code. A unit test framework tool can help to detect defects in functions or methods in source code by providing features such as test case generation, test case execution, test result comparison, test coverage measurement, etc. Some examples of unit test framework tools are JUnit, NUnit, TestNG, etc. The other options are not tools that are likely to detect defects in functions or methods in source code. A configuration management tool is a tool that supports the management and control of different versions and variants of software products or components. A test design tool is a tool that supports the design and generation of test cases based on some criteria or rules. A monitoring tool is a tool that monitors the behavior or performance of a system or component under test. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 10.
NEW QUESTION # 29
ST is a Software Testing organization which utilizes a testing knowledge base. Access to ST knowledge base can be either full or limited. Access level is determined based on ST certification and testing experience as follows:
1. If ST certified, with less than 5 years testing experience - allow limited access
2. If ST certified, 5-10 years of testing experience - allow full access
3. If not ST certified with 5-10 years of testing experience - allow limited access.
What would be the results for:
A - ST certified. 12 years of testing experience
B - Not ST certified. 7 years of testing experience
C - Not ST certified. 3 years of testing experience
- A. A - full access
B - limited access
C - limited access - B. A - full access
B - limited access
C - unknown - C. A - unknown
B - full access
C - unknown - D. A - unknown
B - limned access
C- unknown
Answer: B
Explanation:
The correct answer can be derived by applying the given rules to each case:
A is ST certified and has 12 years of testing experience, which is more than 10 years. Therefore, A does not match any of the rules and the result is unknown.
B is not ST certified and has 7 years of testing experience, which is between 5 and 10 years. Therefore, B matches rule 3 and the result is limited access.
C is not ST certified and has 3 years of testing experience, which is less than 5 years. Therefore, C does not match any of the rules and the result is unknown. Verified Reference: This question does not require any external references, as it is based on logical reasoning.
NEW QUESTION # 30
Which of the following would be the LEAST likely to be used as the basis for a test exit criteria?
- A. Cost of testing performed so far
- B. Number of unfixed defects
- C. Test schedules
- D. Confidence of testers in tested code
Answer: C
Explanation:
Test exit criteria are the conditions or requirements that must be met before testing can be concluded. Test exit criteria are usually defined in the test plan and agreed by the stakeholders. Test exit criteria can be based on various factors, such as test coverage, defect status, quality level, risk level, etc. Test schedules would be the least likely to be used as the basis for test exit criteria, because test schedules are not directly related to the quality or performance of the software product, but rather to the time or resources allocated for testing. Test schedules can be used as the basis for test entry criteria, which are the conditions or requirements that must be met before testing can start. The other options are more likely to be used as the basis for test exit criteria. Cost of testing performed so far can be used as a basis for test exit criteria, because it can indicate the return on investment or the cost-benefit ratio of testing. Confidence of testers in tested code can be used as a basis for test exit criteria, because it can reflect the level of satisfaction or assurance of the testers about the quality or reliability of the software product. Number of unfixed defects can be used as a basis for test exit criteria, because it can indicate the level of risk or impact of the remaining defects on the software product. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 13.
NEW QUESTION # 31
Which of the following statements about reviews are TRUE?
I In walkthroughs the review meeting is typically led by the author.
II Inspection is characterized by an open-ended review meeting
III Preparation before the review meeting is part of informal reviews
IV Management rarely participates in technical review meetings
- A. I, II
- B. II, Ill
- C. I, IV
- D. III, IV
Answer: C
Explanation:
The following statements about reviews are true:
I) In walkthroughs the review meeting is typically led by the author. A walkthrough is a type of review that has a predefined objective and agenda but no formal process or roles. A walkthrough is typically led by the author of the work product under review, who guides the participants through a scenario and solicits feedback.
IV) Management rarely participates in technical review meetings. A technical review is a type of review that has a predefined objective and agenda but no formal process or roles. A technical review is typically performed by peers with technical expertise in order to evaluate technical aspects of a work product. Management rarely participates in technical review meetings, as they may not have sufficient technical knowledge or skills to contribute effectively. The following statements about reviews are false:
II) Inspection is characterized by an open-ended review meeting. An inspection is a type of review that follows a defined process with formal entry and exit criteria and roles and responsibilities for participants. An inspection is characterized by a structured review meeting with a fixed duration and agenda.
III) Preparation before the review meeting is part of informal reviews. Preparation before the review meeting is part of formal reviews, such as inspections or technical reviews. Preparation involves checking
NEW QUESTION # 32
Manager responsibilities in formal review includes ad except one of the following:
- A. Determines if the review objectives have been met
- B. Decide on the execution of reviews
- C. Planning the review
- D. Allocate time for review
Answer: A
Explanation:
A formal review is a type of review that follows a defined process with formal entry and exit criteria and roles and responsibilities for participants. A formal review can have various roles involved, such as manager, moderator, author, reviewer and scribe. The manager responsibilities in formal review include all except one of the following:
Planning the review (correct responsibility)
Determines if the review objectives have been met (incorrect responsibility) Decide on the execution of reviews (correct responsibility) Allocate time for review (correct responsibility) The responsibility of determining if the review objectives have been met belongs to the moderator role, not to the manager role. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 28-29.
NEW QUESTION # 33
Which of the following is a key characteristic of informal reviews?
- A. Low cost
- B. Individual preparation
- C. Kick-off meeting
- D. Metrics analysis
Answer: A
Explanation:
A key characteristic of informal reviews is low cost. Informal reviews are a type of review that does not follow a formal process or have any formal documentation. Informal reviews are usually performed by individuals or small groups of peers or colleagues who have some knowledge or interest in the product under review. Informal reviews can be done at any time and for any purpose, such as checking for errors, clarifying doubts, sharing ideas, etc. Informal reviews have low cost, as they do not require much time, effort, or resources to conduct. The other options are not key characteristics of informal reviews. Kick-off meeting is a characteristic of formal reviews, such as inspections or walkthroughs. Kick-off meeting is a meeting that is held before the review process starts, where the roles and responsibilities of the participants are defined, the objectives and scope of the review are agreed, and the logistics and schedule of the review are planned. Individual preparation is a characteristic of formal reviews, such as inspections or walkthroughs. Individual preparation is an activity that is performed by the reviewers before the review meeting, where they examine the product under review and identify any issues or questions that need to be discussed or resolved during the review meeting. Metrics analysis is a characteristic of formal reviews, such as inspections or walkthroughs. Metrics analysis is an activity that is performed after the review process is completed, where the data and results of the review are collected and analyzed to measure the effectiveness and efficiency of the review, as well as to identify any improvement actions or lessons learned for future reviews. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 9.
NEW QUESTION # 34
The following sentences refer to the 'Standard for Software Test Documentation' specification (IEEE 829).
Which sentence is correct?
- A. Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization
- B. Any deviation from this standard should be approved by management, marketing & development
- 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.
Answer: A
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 Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 16.
NEW QUESTION # 35
Which of the following is a function of a dynamic analysis tool?
- A. Monitor the allocation, use and de-allocation of memory during run-time of a program
- B. Execute programs step-by-step in order to reproduce failures and find corresponding defects
- C. Provide support for release of baselines consisting of configuration items
- D. Provide support for traceability of tests, test results and incidents to source documents
Answer: A
Explanation:
A dynamic analysis tool is a tool that performs analysis of a software product based on its behavior during execution. A dynamic analysis tool can monitor various aspects of a program's run-time performance, such as memory usage, CPU load, response time, or resource leaks. A dynamic analysis tool can monitor the allocation, use and de-allocation of memory during run-time of a program, which can help detect defects such as memory leaks, buffer overflows, or memory corruption. A dynamic analysis tool cannot provide support for traceability of tests, test results and incidents to source documents, as this is a function of a test management tool. A dynamic analysis tool cannot execute programs step-by-step in order to reproduce failures and find corresponding defects, as this is a function of a debugging tool. A dynamic analysis tool cannot provide support for release of baselines consisting of configuration items, as this is a function of a configuration management tool. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 6, page 56-57.
NEW QUESTION # 36
......
ISTQB-CTFL [Mar-2024] Newly Released] ISTQB-CTFL Exam Questions For You To Pass: https://www.passtestking.com/ISTQB/ISTQB-CTFL-practice-exam-dumps.html
For your comfort, PassTestking provides you the convenience of free Foundation Level braindumps demo: https://drive.google.com/open?id=1Uv9SuguYctyR5rLx2rFRb253MbNaM8jw