The configuration management process ensures that all items of testware are identified, version controlled, and tracked for changes. This process helps maintain traceability throughout the test process, ensuring that all test artifacts are managed systematically and changes are monitored effectively.

Valid test objectives include finding defects (i), gaining confidence about the level of quality and providing information (ii), and preventing defects (iii). Debugging the code (iv) is not a valid test objective as it is a part of the development process rather than the testing process.

Metrics are used to measure various aspects of the testing process, such as the percentage of work done in test environment preparation, test case preparation, and whether test milestones were met. However, metrics are not specifically used to apply to the RAD (Rapid Application Development) development model. Metrics focus on providing data to evaluate and improve the testing process rather than applying to specific development methodologies.

The selection of a software development model should be based on the specific characteristics of the product and project. Factors such as project size, complexity, requirements stability, and team expertise influence the choice of the most suitable development model. The ISTQB syllabus explains that there is no one-size-fits-all approach, and the decision should be tailored to the context and needs of the project​​.

Maintenance testing is typically triggered by changes to the operational system, such as data migration, system modification, or system retirement. These triggers require testing to ensure that the changes do not negatively impact the existing functionality. However, the introduction of a test management tool does not directly affect the operational system and is not considered a trigger for maintenance testing​​.

Common metrics used for monitoring test preparation and execution typically include quantitative measures such as the number of test cases passed and failed, the percentage of planned test cases designed, and the percentage of tasks completed in test environment preparation. These metrics provide insights into the progress and effectiveness of the testing process. However, the number of test plan review comments is not a typical metric for this purpose, as it does not directly measure the progress or quality of test execution​​.

Writing test summary reports is typically the responsibility of a test leader or manager, who consolidates testing activities and results to communicate with stakeholders. Testers are more involved in preparing and acquiring test data, setting up and checking the test environment, and reviewing tests developed by others. These tasks are more hands-on and technical, aligning with the role of a tester​​ .

Top of Form

Bottom of Form

To meet the test plan requirements and logical dependencies, the test schedule should start with re-tests (those that have previously failed), followed by the highest priority tests. Additionally, tests should be scheduled to create necessary test data for subsequent tests. In this case, test e (log in as admin user and create a standard user) must be done first as it is necessary to perform all other actions. Following this, test a (log in as standard user and create customer account) creates the standard user needed for subsequent actions. Then, the highest priority test d (order two items or more), which has failed before, should be executed next, followed by test c (create invoice for order), and finally test b (order one item)​​.

Functional and structural testing can be applied at all test levels. Functional testing focuses on verifying that the software behaves as expected based on the requirements, while structural testing examines the internal structure and workings of the software. These testing approaches are complementary and can be used together at various stages of testing, including component, integration, system, and acceptance testing. Applying both types of tests ensures a comprehensive evaluation of the software's functionality and internal structure​​.

Top of Form

Bottom of Form

According to the decision table, Test Case 1 is valid because an employee who is not a car or motorcycle driver cannot claim expenses, as shown in Rule 1. Test Case 3 is valid because a motorcycle driver can claim expenses, as indicated in Rule 2, with expenses claim band A. However, Test Case 2 is invalid because, according to Rule 5, a car driver with a diesel engine greater than 1600cc cannot claim expenses. The expected result should be that the expense claim is not allowed, not band C​​.