Which steps define an end-to-end test for address creation flow?

Which steps define an end-to-end test for address creation flow?

• A. Simulate user input, validation, normalization, optional geocoding, saving, and auditing, with expected confirmation
• B. Only input and saving
• C. Only validation and formatting
• D. Only auditing

Answer: (A)

End-to-end testing for an address creation flow means validating the entire user journey from start to finish, ensuring every component works together and the user sees the expected outcome. This includes simulating user input, running validation to catch errors, normalizing the address into a consistent format, optionally performing geocoding to obtain coordinates, saving the record, emitting auditing for traceability, and finally presenting the confirmation to the user. Each part matters: input simulates real-world use; validation catches invalid data; normalization enforces a standard representation; geocoding tests integration with the geocoding service; saving checks persistence; auditing verifies traceability; and the final confirmation verifies the user-facing outcome. Other options omit essential steps, such as missing validation, normalization, auditing, or user confirmation, so they don’t exercise the full flow. Therefore, including all these steps with an expected confirmation best defines an end-to-end test.