最新的ISTQB Agile Public Sector - ISTQB-Agile-Public免費考試真題

A. The automation tests failed frequently without any logs to help in debugging the failure reason.

B. For the last sprint the estimated and actual effort were much higher than the team capacity.

C. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.

D. The build process was slow and this often caused delays waiting for the build to complete.

A. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.

B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.

C. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.

D. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.

A. iv, v

B. i. v

C. i. iv

D. ii, iii

A. Having at least once a day an automated build and test process that detects integration errors early and quickly.

B. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.

C. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.

D. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.

A. User story testing - test that the user can enter an income amount and get a result

B. State transition testing - test all states of income entry.

C. Equivalence partitioning - test with low, medium and high income.

D. Statement testing - test all statements in income calculation.