BA-201 · Question #207
Cloud Kicks is creating a new lead conversion process in Sales Cloud. During a recent sprint, the business analyst created user stories related to the Opportunity object. Test scripts were created…
The correct answer is A. Functionality on interconnected objects should be part of UAT. The test scripts were scoped only to the lead conversion process, but the Opportunity object is also used independently (manual creation). Changes made to support lead conversion can affect related workflows, validation rules, or triggers that apply to all Opportunity creation…
Question
Cloud Kicks is creating a new lead conversion process in Sales Cloud. During a recent sprint, the business analyst created user stories related to the Opportunity object. Test scripts were created for the lead conversion process. All of the test scripts passed and the new functionality was deployed. After deployment, end users reported error messages when manually creating new Opportunities. Which area of user acceptance testing (UAT) was overlooked?
Options
- AFunctionality on interconnected objects should be part of UAT.
- BSeveral teams should be part of UAT to represent multiple viewpoints.
- CEnd users who are experts in that functionality should participate in UAT.
How the community answered
(23 responses)- A74% (17)
- B17% (4)
- C9% (2)
Explanation
The test scripts were scoped only to the lead conversion process, but the Opportunity object is also used independently (manual creation). Changes made to support lead conversion can affect related workflows, validation rules, or triggers that apply to all Opportunity creation paths. UAT must cover interconnected objects and adjacent processes, not just the primary workflow being implemented. Options B and C describe valid UAT practices but do not address the root cause: the test scope failed to include the broader impact on the Opportunity object.
Topics
Community Discussion
No community discussion yet for this question.