ISTQB CTFL-2018 Practice Test - Questions Answers, Page 14

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:

To ensure the product works as expected, which means verifying that the product meets the functional and non-functional requirements agreed upon by the users or customers and the development team during each iteration or sprint of the Agile development process.

To assess the overall quality of the product, which means evaluating how well the product satisfies the quality attributes that are important for the users or customers, such as usability, performance, reliability, security, etc.

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

Testers identify defects, developers locate and correct defects, testers confirm the correction has cleared the original defect. Debugging is the process of finding and fixing defects in a software product by analyzing its code or behavior. Debugging is usually performed by developers who have access to and knowledge of the code or structure of the software product. Debugging involves locating and correcting defects identified by testers during testing activities, and verifying that the correction has cleared the original defect without introducing new defects. Testers can also participate in debugging by providing information about how to reproduce defects, what are the expected results, what are the actual results, etc., and by confirming that defects have been fixed after debugging. A detailed explanation of debugging can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], page 6.

The fundamental test process is a generic model that describes the main activities and tasks involved in testing. The fundamental test process consists of five phases: planning and control, analysis and design, implementation and execution, evaluation of exit criteria and reporting, and test closure activities. Implementation and execution is the phase where test cases and test procedures are implemented according to test specifications and executed on the system or component under test using test tools or manual methods. Implementation and execution also involves verifying that the test environment set up is correct, which means ensuring that the test environment (such as hardware, software, network, data, etc.) is ready and suitable for testing the system or component under test. A detailed explanation of implementation and execution can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 19-21.

Independence from the production process is a characteristic that is most likely to promote effective software testing1.Independence from the production process means that the testers are not involved in the development or maintenance of the software product under test, and thus can provide an unbiased and objective view of its quality1.Independence from the production process can also help to avoid conflicts of interest, reduce confirmation bias, increase defect detection, and improve test coverage1. Therefore, independence from the production process is a characteristic that is most likely to promote effective software testing.

The choice of software development model depends on product and project characteristics1.A software development model is a framework that defines the activities, tasks, roles, and deliverables of a software project1.There are various software development models, such as waterfall, V-model, iterative, incremental, agile, etc1.The choice of software development model depends on product and project characteristics, such as size, complexity, scope, requirements, quality attributes, risks, resources, schedule, budget, etc1.Different software development models have different advantages and disadvantages for different types of products and projects1. Therefore, the choice of software development model depends on product and project characteristics.

Testers should be involved in reviewing a UAT specification as soon as the UAT specification has been drafted1.UAT stands for user acceptance testing, which is a type of testing that verifies that the software product meets the acceptance criteria and expectations of the end users or customers1.A UAT specification is a document that defines the scope, objectives, approach, and criteria for UAT1.Testers should be involved in reviewing a UAT specification as soon as the UAT specification has been drafted, as this can help to ensure that the UAT specification is clear, complete, consistent, testable, and aligned with the user requirements1.Testers can also provide feedback and suggestions to improve the UAT specification and avoid potential issues or conflicts during UAT execution1. Therefore, testers should be involved in reviewing a UAT specification as soon as the UAT specification has been drafted.

Integration testing is a test level that accurately defines the integration testing test level1.Integration testing is a type of testing that verifies that different components or systems work together correctly and consistently1.The test basis for integration testing includes software and system design documents that specify how the components or systems are integrated and interact with each other1.The test objects for integration testing include interfaces between components or systems that enable data exchange or communication1.The tests for integration testing concentrate on the interactions between different parts of a system and check for functional, performance, reliability, security, compatibility, and interoperability issues1. Therefore, integration testing is a test level that accurately defines the integration testing test level.

Functional testing to test security at the system level, load testing at the system level to ensure the system availability is acceptable, regression testing at all levels, structure based testing at the component level only are the test types that will be required during the development1. A bank is developing a new service that will be delivered via the web. The user interactions are defined as a set of use cases and the service is designed to be available continuously 24/7. In view of the challenging characteristics of the service, the test manager has decided that the code should be thoroughly tested at component level. Therefore, the following test types will be required during the development:

Functional testing to test security at the system level: This type of testing verifies that the software product performs its intended functions according to the user requirements and expectations1.Security is one of the functional aspects that needs to be tested at the system level, as it ensures that the software product protects itself from unauthorized access or harm1.

Load testing at the system level to ensure the system availability is acceptable: This type of testing verifies that the software product can handle the expected or peak load of users or transactions without degrading its performance or functionality1.Availability is one of the quality attributes that needs to be tested at the system level, as it measures how well the software product performs its intended functions under specified conditions without interruption or failure1.

Regression testing at all levels: This type of testing verifies that previously tested software still performs correctly after changes or defect corrections1.Regression testing is required at all levels of testing, as changes or defect corrections can introduce new defects or affect existing functionality1.

Structure based testing at the component level only: This type of testing uses the structure or logic of the source code as a test basis to derive test cases and measure test coverage1.Structure based testing is required at the component level only, as the test manager has decided that the code should be thoroughly tested at component level to ensure its quality and reliability1.

Functional and structural tests are alternative test types that may be used separately or together at B. All test levels. Functional testing is a type of testing that verifies the functionality of the system or component under test against its requirements or specifications. Functional testing focuses on what the system or component does, not how it does it. Structural testing is a type of testing that verifies the structure or code of the system or component under test. Structural testing focuses on how the system or component does it, not what it does. Functional and structural testing can be used separately or together at any test level, such as unit testing, integration testing, system testing, acceptance testing, etc. Functional and structural testing can complement each other by providing different perspectives and coverage of the system or component under test. A detailed explanation of functional and structural testing can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 25-26.