CTFL_Syll2018 iSQI Exam Lab Questions

•  The test objectives for user acceptance testing of the first release of a new software product aimed at a general market and built using Agile methods are D. c and d. User acceptance testing is a level of testing that involves users or customers validating that the software product meets their needs and expectations before accepting it for use or deployment. User acceptance testing can have different objectives depending on the context and purpose of the software product. For a new software product aimed at a general market and built using Agile methods, some possible objectives are:

A detailed explanation of user acceptance testing can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 79-80.

Testing can demonstrate that there are defects in the software, by finding and reporting them. Testing cannot demonstrate that there are no defects, because it is impossible to test all possible scenarios and inputs. Testing cannot demonstrate that the software is correct, because correctness is a subjective and relative concept that depends on the expectations and requirements of the stakeholders. Testing cannot demonstrate that there are no hidden defects in the software, because hidden defects are those that are not detected by testing or other quality assurance activities.

Static code analysis is a technique that examines the source code or other software artifacts without executing them, and can detect defects, vulnerabilities, code smells, and deviations from standards early in the development process1. According to the ISTQB syllabus, one of the benefits of static testing is early defect detection2, which can reduce the cost and effort of fixing them later.