In Agile projects, test cases may need to be refactored to improve their clarity and maintainability. This process makes the test cases easier to understand and cheaper to modify, which is essential in Agile environments where changes are frequent and rapid. Refactoring test cases ensures that they remain effective and efficient as the codebase evolves, allowing for quick adjustments in response to new requirements or changes in the system under test.
References = The ISTQB Advanced Level Agile Technical Tester documents emphasize the importance of refactoring test cases in Agile projects to maintain their effectiveness and efficiency1.

The main flaw in the proposed test charter is that it does not cover the main functionality of the user story. The user story focuses on the customer wanting to be informed about the delivery time of their items so they can plan to be home. The proposed charter only tests for the absence of a shipping fee and does not address whether the system provides the customer with the delivery time information.
References = The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of aligning test charters with the user story's main functionality to ensure that tests provide adequate coverage12. It is crucial in Agile methodologies to create and evaluate testable acceptance criteria that reflect the user story's objectives12.

* Common Test Automation Challenges:As test suites grow, execution time often increases, leading to delays in feedback cycles. This can make it challenging to run tests frequently, especially in continuous integration pipelines.
* Scalability Concerns:Longer execution times can affect productivity and may require optimization or selective test execution strategies.
* Conclusion:Option B is correct as it describes a common scalability problem in automation suites.

Updating the test automation suite during each iteration as the code is received ensures that the suite evolves with the software. It allows for immediate feedback on the impact of changes, supports continuous integration, and helps in identifying defects early in the development process. This practice is in line with Agile principles, which advocate for continuous testing and integration to improve quality and reduce the time to market1.
References = The ISTQB Advanced Level Agile Technical Tester documents outline the importance of maintaining and updating test automation suites in an Agile environment to support continuous integration and delivery, and to ensure that the tests provide adequate coverage throughout the development cycle2.

Quantitative questionnaires are best suited for eliciting non-functional requirements from a large number of stakeholders. This is because they allow for the collection of measurable, statistical data that can be analyzed to understand the stakeholders' needsregarding system qualities like performance, usability, and reliability. These questionnaires can be designed to include specific questions about non-functional aspects, which can then be quantitatively assessed to inform the acceptance criteria1.
References = The ISTQB Advanced Level Agile Technical Tester syllabus and study resources emphasize the importance of understanding and defining both functional and non-functional requirements in Agile environments. They outline various elicitation techniques that can be used to gather these requirements, including the use of questionnaires for collecting quantitative data23.