A hospital books a supply request in one app, and finance places that same request on a hold list when the amount needs review. Tests of each screen pass on their own. What test should the architect add before go-live?
Select an answer to reveal the explanation.
Short Explanation
A lamp that lights on the bench can still fail once it is wired into the building. You book a supply request in a test and you confirm that same request shows on the finance hold list. Stopping at the booking screen leaves the handoff unproved.
Full Explanation
An end-to-end test is required when the process crosses apps, even if each screen already passes alone. The hospital books a supply request and finance is supposed to place that same request on the hold list, so the test books the request and then finds that same request on the finance hold list. A test that books the supply request and stops, without opening the finance hold list at all, does not check the step that failed in the business process. A review of each copilot's description text, with no supply request booked in either application, inspects labels and creates no request to find. A chat-volume count that totals messages and does not book a supply request or open the hold list measures conversation traffic and says nothing about the hold. Screen tests can stay. They do not replace the path from the booking to the hold list. Exam caveat: the hold list is the finance side of this hospital's process, not a second booking screen. The test has to open it. Operational check: book one supply request in the test company and match its identifier on the finance hold list before go-live is allowed.