Free Sample Questions to Practice ISTQB-CTFL Certification Test Engine [May-2024]
2024 Valid ISTQB-CTFL Real Exam Questions, practice Foundation Level
NEW QUESTION # 31
Which of the following statements is not correct?
- A. Testing is often seen as a destructive activity instead of constructive activity
- B. Identifying defects may be perceived as criticism against product
- C. Looking for defects in a system may require Ignoring system details
- D. Looking for defects in system requires professional pessimism and curiosity
Answer: C
Explanation:
* Looking for defects in a system does not require ignoring system details, but rather paying attention to them and understanding how they affect the system's quality, functionality, and usability. Ignoring system details could lead to missing important defects or testing irrelevant aspects of the system.
* Identifying defects may be perceived as criticism against product, especially by the developers or stakeholders who are invested in the product's success. However, identifying defects is not meant to be a personal attack, but rather a constructive feedback that helps to improve the product and ensure its alignment with the requirements and expectations of the users and clients.
* Looking for defects in system requires professional pessimism and curiosity, as testers need to anticipate and explore the possible ways that the system could fail, malfunction, or behave unexpectedly.
Professional pessimism means being skeptical and critical of the system's quality and reliability, while curiosity means being eager and interested in finding out the root causes and consequences of the defects.
* Testing is often seen as a destructive activity instead of constructive activity, as it involves finding and reporting the flaws and weaknesses of the system, rather than creating or enhancing it. However, testing is actually a constructive activity, as it contributes to the system's improvement, verification, validation, and optimization, and ultimately to the delivery of a high-quality product that meets the needs and expectations of the users and clients.
References =
* ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 7-8, 10-11, 13-14, 16-17, 19-20,
22-23, 25-26, 28-29, 31-32, 34-35, 37-38, 40-41, 43-44, 46-47, 49-50, 52-53, 55-56, 58-59, 61-62,
64-65, 67-68, 70-71, 73-74, 76-77, 79-80, 82-83, 85-86, 88-89, 91-92, 94-95, 97-98, 100-101, 103-104,
106-107, 109-110, 112-113, 115-116, 118-119, 121-122, 124-125, 127-128, 130-131, 133-134, 136-137,
139-140, 142-143, 145-146, 148-149, 151-152, 154-155, 157-158, 160-161, 163-164, 166-167, 169-170,
172-173, 175-176, 178-179, 181-182, 184-185, 187-188, 190-191, 193-194, 196-197, 199-200, 202-203,
205-206, 208-209, 211-212, 214-215, 217-218, 220-221, 223-224, 226-227, 229-230, 232-233, 235-236,
238-239, 241-242, 244-245, 247-248, 250-251, 253-254, 256-257, 259-260, 262-263, 265-266, 268-269,
271-272, 274-275, 277-278, 280-281, 283-284, 286-287, 289-290, 292-293, 295-296, 298-299, 301-302,
304-305, 307-308, 310-311, 313-314, 316-317, 319-320, 322-323, 325-326, 328-329, 331-332, 334-335,
337-338, 340-341, 343-344, 346-347, 349-350, 352-353, 355-356, 358-359, 361-362, 364-365, 367-368,
370-371, 373-374, 376-377, 379-380, 382-383, 385-386, 388-389, 391
NEW QUESTION # 32
Which of the following is a typical product risk?
- A. Problem in defining the right requirements
- B. Low quality of the configuration data, test data and tests
- C. Poor usability of the software
- D. A problem in the code developed by a 3rd party
Answer: C
Explanation:
A typical product risk involves issues directly related to the software product's functionality, performance, usability, reliability, etc. Option A, "Poor usability of the software," directly impacts the end-user's interaction with the software and is a quality attribute of the product itself, making it a product risk. Options B, "A problem in the code developed by a 3rd party," C, "Low quality of the configuration data, test data and tests," and D, "Problem in defining the right requirements," can be considered either product or project risks depending on the context, but option A is the most directly associated with a typical product risk concerning the quality and usability of the software.
NEW QUESTION # 33
Can "cost" be regarded as Exit criteria?
- A. No The cost of testing cannot be measured effectively, so it is incorrect to use cost as an exit criterion
- B. Yes. Going by cost as an exit criterion constrains the testing project which will hello achieve the desired quality level defined for the project
- C. Yes. Spending too much money on test ng will result in an unprofitable product, and having cost as an exit criterion helps avoid this
- D. No. The financial value of product quality cannot be estimated, so it is incorrect to use cost as an exit criterion
Answer: C
Explanation:
Cost can be regarded as an exit criterion for testing, because it is a factor that affects the profitability and feasibility of the software product. Testing is an investment that aims to improve the quality and reliability of the software product, but it also consumes resources, such as time, money, and human effort. Therefore, testing should be planned and executed in a way that balances the cost and benefit of testing activities. Having cost as an exit criterion helps to avoid spending too much money on testing, which may result in an unprofitable product or a loss of competitive advantage. Cost can also help to prioritize and focus the testing efforts on the most critical and valuable features andfunctions of the software product. However, cost should not be the only exit criterion for testing, as it may not reflect the true quality and risk level of the software product. Other exit criteria, such as defect rate, test coverage, user satisfaction, etc., should also be considered and defined in the test plan.
The other options are incorrect, because they either deny the importance of cost as an exit criterion, or they make false or unrealistic assumptions about the cost of testing. Option B is incorrect, because the financial value of product quality can be estimated, for example, by using cost-benefit analysis, return on investment, or cost of quality models. Option C is incorrect, because going by cost as an exit criterion does not necessarily constrain the testing project or help achieve the desired quality level. Cost is a relative and variable factor that depends on the scope, complexity, and context of the software product and the testing project. Option D is incorrect, because the cost of testing can be measured effectively, for example, by using metrics, such as test effort, test resources, test tools, test environment, etc.
NEW QUESTION # 34
During component testing of a program if 100% decision coverage is achieved, which of the following coverage criteria is also guaranteed to be 100%?
- A. 100% Stale transition coverage
- B. 100% Equivalence class coverage
- C. 100% Boundary value coverage
- D. 100% Statement coverage
Answer: D
Explanation:
Statement coverage is a structural coverage metric that measures the percentage of executable statements in the source code that are executed by a test suite1. Decision coverage is another structural coverage metric that measures the percentage of decision outcomes (such as branches or conditions) in the source code that are executed by a test suite1. Decision coverage is a stronger metric than statement coverage, because it requires that every possible outcome of each decision is tested, while statement coverage only requires that every statement is executed at least once2. Therefore, if a test suite achieves 100% decision coverage, it also implies that it achieves 100% statement coverage, because every statement in every branch or condition must have been executed. However, the converse is not true: 100% statement coverage does not guarantee 100% decision coverage, because some branches or conditions may have multiple outcomes that are not tested by the test suite2. For example, consider the following pseudocode:
if (x > 0) then print("Positive") else print("Non-positive") end if
A test suite that executes this code with x = 1 and x = -1 will achieve 100% statement coverage, because both print statements are executed. However, it will not achieve 100% decision coverage, because the condition x > 0 has only been tested with two outcomes: true and false. The third possible outcome, x = 0, has not been tested by the test suite. Therefore, the test suite may miss a potential bug or error in the condition or the branch.
The other options, such as stale transition coverage, equivalence class coverage, and boundary value coverage, are not guaranteed to be 100% by achieving 100% decision coverage. Stale transition coverage is a structural coverage metric that measures the percentage of transitions between states in a state machine that are executed by a test suite3. Equivalence class coverage is a functional coverage metric that measures the percentage of equivalence classes (or partitions) of input or output values that are tested by a test suite4. Boundary value coverage is another functional coverage metric that measures the percentage of boundary values (or extreme values) of input or output ranges that are tested by a test suite4. These metrics are independent of decision coverage, because they are based on different aspects of the system under test, such as its behavior, functionality, or specification. Therefore, achieving 100% decision coverage does not imply achieving 100% of any of these metrics, and vice versa. Reference = ISTQB Certified Tester Foundation Level Syllabus v4.0, Test Coverage in Software Testing - Guru99, Structural Coverage Metrics - MATLAB & Simulink - MathWorks India, Test Design Coverage in Software Testing - GeeksforGeeks.
NEW QUESTION # 35
Which of the following statements regarding inspection isNOTtrue?
- A. The main purpose of an inspection is to find solutions to the problems.
- B. An inspection can be performed by peers.
- C. An inspection shall follow a formal process based on rules and checklists with entry and exit criteria
- D. An inspection may be led by a trained moderator who shall not be the author.
Answer: A
Explanation:
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 can be performed by peers with different roles, such as moderator, author, reviewer and scribe. The following statement about inspection is not true:
* B) The main purpose of an inspection is to find solutions to the problems. This statement is not true, as the main purpose of an inspection is to find defects or issues in a work product, not to find solutions to the problems. Finding solutions to the problems is a debugging or problem-solving activity that is usually performed by the author or developer after receiving the inspection report. The following statements about inspection are true:
* A) An inspection may be led by a trained moderator who shall not be the author. This statement is true, as an inspection requires a moderator role who leads the inspection process and ensures that it follows the rules and standards. The moderator should be trained in inspection techniques and should not be the author of the work product under inspection, in order to avoid bias or conflict of interest.
* C) An inspection can be performed by peers. This statement is true, as an inspection involves peer review, which means that the work product under inspection is evaluated by people who have similar roles or expertise as the author, but who are not directly involved in creating or modifying the work product.
* D) An inspection shall follow a formal process based on rules and checklists with entry and exit criteria.
This statement is true, as an inspection follows a formal process that consists of six main steps:
planning, kick-off meeting, individual preparation, review meeting, rework and follow-up. Each step has defined rules and checklists to guide the participants and ensure consistency and quality. Each step also has entry and exit criteria to ensure that the prerequisites and objectives are met before moving to the next step. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 28-29.
NEW QUESTION # 36
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. Confidence of testers in tested code
- D. Test schedules
Answer: D
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 13.
NEW QUESTION # 37
Which of the following statements about test reports are TRUE?
I Test reports shall be approved by the test team.
II. Test reports shall give stakeholders information as basis for decisions.
Ill Test reports shall summarize what happened through a period of testing.
IV. Test reports shall be approved by the development team, the test team and the customer
V. Test reports shall include information about remaining risks.
- A. II, III, IV
- B. I, II, IV
- C. I, III, v
- D. II, III, V
Answer: D
Explanation:
Statements II, III and V are true about test reports. Test reports are documents that provide information on the results and status of testing activities for a given period or phase. Test reports should give stakeholders information as basis for decisions, such as whether to release the software product, whether to continue testing, whether to change the scope or priorities of testing, etc. Test reports should summarize what happened through a period of testing, such as what test cases were executed, what defects were found, what risks were identified, what issues were encountered, what achievements were made, etc. Test reports should include information about remaining risks, such as what defects are still open, what test cases are still pending, what functionalities are still untested, what uncertainties are still unresolved, etc. Statements I and IV are not true about test reports. Test reports do not need to be approved by the test team, the development team, or the customer, unless it is specified by the test policy or the test plan. Test reports only need to be reviewed and verified by the test leader or the test manager before being distributed to the intended recipients. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
NEW QUESTION # 38
A test engineer finds a defect while testing. After the developer has fixed the defect, the test engineer decides to re-run a complete section of the tests. Which of the following is correct?
- A. The lest engineer should not re-run the tests, as they have already been run, and results recorded.
- B. The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix.
- C. The test engineer should not re-run the tests, they should be part of the developer tests.
- D. The test engineer should re-run the tests, because the defect shows that the test cases need to be updated.
Answer: B
Explanation:
The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix. This is also known as regression testing, which is a type of testing that verifies that previously tested software still performs correctly after a change. Regression testing helps to detect any side effects or unintended consequences of a fix or a modification. The other options are incorrect reasons for re-running the tests. The test engineer should not re-run the tests, as they have already been run, and results recorded, because this ignores the possibility of new defects caused by the fix. The test engineer should not re-run the tests, they should be part of the developer tests, because this assumes that developer tests are sufficient and reliable, which may not be true. The test engineer should not re-run the tests, because the defect shows that the test cases need to be updated, because this does not address the impact of the fix on other test cases or functionalities. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 41.
NEW QUESTION # 39
Which of the following is correct with regards to debugging?
- A. Debugging identifies the cause of a failure
- B. Debugging is considered part of the testing activities
- C. Debugging is often performed by test engineers
- D. Debugging is intended to find as many defects as possible in the code
Answer: A
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 References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 1, page 6.
NEW QUESTION # 40
A test engineer finds a defect while testing. After the developer has fixed the defect, the test engineer decides to re-run a complete section of the tests. Which of the following is correct?
- A. The lest engineer should not re-run the tests, as they have already been run, and results recorded.
- B. The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix.
- C. The test engineer should not re-run the tests, they should be part of the developer tests.
- D. The test engineer should re-run the tests, because the defect shows that the test cases need to be updated.
Answer: B
Explanation:
The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix. This is also known as regression testing, which is a type of testing that verifies that previously tested software still performs correctly after a change. Regression testing helps to detect any side effects or unintended consequences of a fix or a modification. The other options are incorrect reasons for re-running the tests. The test engineer should not re-run the tests, as they have already been run, and results recorded, because this ignores the possibility of new defects caused by the fix. The test engineer should not re-run the tests, they should be part of the developer tests, because this assumes that developer tests are sufficient and reliable, which may not be true. The test engineer should not re-run the tests, because the defect shows that the test cases need to be updated, because this does not address the impact of the fix on other test cases or functionalities. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 41.
NEW QUESTION # 41
Which of the following statements about testware are correct?
I When closing the test activities, all the testware resources can be uninstalled and released II All the testware should be subject to Configuration Management III. The testware. at the end of the project, should be transferred to the organization responsible for maintenance IV The developers are responsible for the correct installation of the testware
- A. I, IV
- B. II, Ill
- C. I, Ill
- D. II, IV
Answer: B
Explanation:
Testware is a term that refers to all artifacts produced during the testing process, such as test plans, test cases, test scripts, test data, test results, defect reports, etc. The following statements about testware are correct:
II) All the testware should be subject to Configuration Management. Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle. Configuration management applies to all testware, as it helps ensure their quality and consistency, track their changes and defects, control their versions and access rights, and link them to other artifacts.
III) The testware at the end of the project should be transferred to the organization responsible for maintenance. Maintenance testing is testing performed on a software product after delivery to correct defects or improve performance or other attributes. Maintenance testing requires testware from previous testing activities or phases, such as test cases, test data, test results, etc. Therefore, the testware at the end of the project should be transferred to the organization responsible for maintenance testing, such as support team or maintenance team. The following statements about testware are incorrect:
I) When closing the test activities, all the testware resources can be uninstalled and released. This statement is incorrect, as some testware resources may still be needed for future testing activities or phases, such as maintenance testing or regression testing. Therefore, when closing the test activities, some testware resources should be archived and stored for future use, while others can be uninstalled and released.
IV) The developers are responsible for the correct installation of the testware. This statement is incorrect, as the testers are responsible for the correct installation of the testware. The testers should ensure that they have access to all necessary testware resources and that they are installed and configured properly before starting the test execution. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 6, page 58-61.
NEW QUESTION # 42
A Test Manager conducts risk assessment for a project. One of the identified risks is: The sub-contractor may fail to meet his commitment". If this risk materializes. it will lead to delay in completion of testing required for the current cycle.
Which of the following sentences correctly describes the risk?
- A. It is a product risk since any risk associated with development timeline is a product risk.
- B. It is a object risk since successful completion of the object depends on successful and timely completion of the tests
- C. It is no longer a risk for the Test Manager since an independent party (the sub-contractor) is now managing it
- D. It is a product risk since default on part of the sub-contractor may lead to delay in release of the product
Answer: D
Explanation:
* A product risk is a risk that affects the quality or timeliness of the software product being developed or tested1. Product risks are related to the requirements, design, implementation, verification, and maintenance of the software product2.
* The risk of the sub-contractor failing to meet his commitment is a product risk, as it could cause a delay in the completion of the testing required for the current cycle, which in turn could affect the release date of the product. The release date is an important aspect of the product quality, as it reflects the customer satisfaction and the market competitiveness of the product3.
* The other options are not correct because:
* A. It is not true that any risk associated with development timeline is a product risk. Some risks could be project risks, which are risks that affect the management or control of the software project, such as budget, resources, schedule, or communication1. For example, a risk of losing a key project stakeholder is a project risk, not a product risk.
* B. It is not true that the risk is no longer a risk for the Test Manager since an independent party is managing it. The Test Manager is still responsible for ensuring that the testing activities are completed according to the test plan and the quality objectives4. The Test Manager should monitor and control the sub-contractor's performance and communicate with him regularly to identify and mitigate any potential issues or deviations5.
* C. It is not clear what is meant by "object" in this option, but it could be interpreted as the software system under test or the test object6. In any case, the risk is not an object risk, as it does not affect the successful completion of the object, but rather the successful completion of the testing of the object. An object risk could be a risk that affects the functionality, reliability, usability, efficiency, maintainability, or portability of the software system under test2. For example, a risk of the software system having a high complexity or a low testability is an object risk, not a product risk.
References =
* 1 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97
* 2 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98
* 3 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 99
* 4 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 100
* 5 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 101
* 6 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 102
NEW QUESTION # 43
A calculator software is used to calculate the result for 5+6.
The user noticed that the result given is 6.
This is an example of;
- A. Mistake
- B. Fault
- C. Error
- D. Failure
Answer: D
Explanation:
According to the ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 18, a failure is "an event in which a component or system does not perform a required function within specified limits". In this case, the calculator software does not perform the required function of calculating the correct result for 5+6 within the specified limits of accuracy and precision. Therefore, this is an example of a failure.
The other options are incorrect because:
* A mistake is "a human action that produces an incorrect result" (page 25). A mistake is not an event, but an action, and it may or may not lead to a failure. For example, a mistake could be a typo in the code, a wrong assumption in the design, or a misunderstanding of the requirement.
* A fault is "a defect in a component or system that can cause the component or system to fail to perform its required function" (page 16). A fault is not an event, but a defect, and it may or may not cause a failure. For example, a fault could be a logical error in the code, a missing specification in the design, or a contradiction in the requirement.
* An error is "the difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition" (page 15). An error is not an event, but a difference, and it may or may not result in a failure. For example, an error could be a rounding error in the calculation, a measurement error in the observation, or a deviation error in the condition.
References = ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 15-18, 25; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 96, page 34.
NEW QUESTION # 44
Which ONE of the following statements does NOT describe how testing contributes to higher quality?
- A. Properly designed tests that pass reduce the level of risk in a system.
- B. Software testing identifies defects, which can be used to improve development activities.
- C. The testing of software demonstrates the absence of defects.
- D. Performing a review of the requirement specifications before implementing the system can enhance quality.
Answer: C
Explanation:
* The testing of software does not demonstrate the absence of defects, but rather the presence of defects or the conformance of the software to the specified requirements1. Testing can never prove that the software is defect-free, as it is impossible to test all possible scenarios, inputs, outputs, and behaviors of the software2. Testing can only provide a level of confidence in the quality of the software, based on the coverage, effectiveness, and efficiency of the testing activities3.
* The other options are correct because:
* A. Properly designed tests that pass reduce the level of risk in a system, as they verify that the system meets the expected quality attributes and satisfies the needs and expectations of the users and clients4. Risk is the potential for loss or harm due to the occurrence of an undesirable event5. Testing can help to identify, analyze, prioritize, and mitigate the risks associated with the software product and project6.
* C. Software testing identifies defects, which can be used to improve development activities, as they provide feedback on the quality of the software and the effectiveness of the development processes7. Defects are flaws or errors in the software that cause it to deviate from the expected or required results or behavior. Testing can help to detect, report, track, and resolve the defects, and prevent them from recurring in the future.
* D. Performing a review of the requirement specifications before implementing the system can enhance quality, as it can ensure that the requirements are clear, complete, consistent, testable, and aligned with the needs and expectations of the users and clients. Requirements are the specifications of what the software should do and how it should do it. Testing can help to validate that the requirements are met by the software, and verify that the software is implemented according to the requirements.
References =
* 1 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 10
* 2 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 11
* 3 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 12
* 4 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 13
* 5 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97
* 6 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98
* 7 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 14
* [8] ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 15
* [9] ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 16
* [10] ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 17
* [11] ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 18
* [12] ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 19
NEW QUESTION # 45
Which type of software development product can undergo static testing?
- A. Static testing is done only on the code as part of the "code review" sessions Other documents are reviewed, but not by static testing.
- B. Any software development product can undergo static testing, including requirements specifications, design specifications and code.
- C. Static testing is done only on the requirements You need to execute the software in order to find defects in the code.
- D. Static tests should be performed on the installation and user guide documents as these documents are used by the end user.
Answer: B
Explanation:
Static testing is a form of testing that does not involve executing the software, but rather analyzing it for defects, errors, or violations of standards. Static testing can be applied to any software development product, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing can be done by using various techniques such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.
NEW QUESTION # 46
Which of the following isNOTa common objective of testing?
- A. Debugging the software to find the reason for defects
- B. Preventing defects
- C. Finding defects in the software
- D. Providing information on the status of the system
Answer: A
Explanation:
Debugging the software to find the reason for defects is not a common objective of testing, but rather a task of development or maintenance. Debugging is a process of locating and fixing errors in the software code, while testing is a process of finding and reporting defects in the software behavior or quality. Testing does not aim to fix defects, but rather to provide information on their existence and impact. The other options are common objectives of testing. Finding defects in the software is one of the main objectives of testing, as it helps to improve the quality and reliability of the software. Preventing defects is another objective of testing, as it helps to avoid rework and reduce costs and risks. Providing information on the status of the system is another objective of testing, as it helps to support decision making and risk management. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 3.
NEW QUESTION # 47
In maintenance testing, what is the relationship between impact analysis and regression testing?
- A. There is no relationship between impact analysis and regression testing.
- B. Impact analysis requires a regression testing for only the tests that have detected faults in previous SW release
- C. Impact analysis requires a regression testing for all program elements which were newly integrated (new functionalities).
- D. The impact analysis is used to evaluate the amount of regression testing to be performed.
Answer: D
Explanation:
In maintenance testing, the relationship between impact analysis and regression testing is that the impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product's functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regressiontesting to be performed.
Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 20.
NEW QUESTION # 48
......
Genuine ISTQB-CTFL Exam Dumps Free Demo Valid QA's: https://www.exam4labs.com/ISTQB-CTFL-practice-torrent.html
Latest Success Metrics For Actual ISTQB-CTFL Exam (Updated 132 Questions): https://drive.google.com/open?id=1rp1j4E_AQ4xoPxPX9FbC_DZz9u5hvTI4