How do people manage BAT (Business Acceptance Testing) here? I’ve been asked to come up with a process that we can use for future features that we release. This is my current idea.
- Development team alongside stakeholders come up with suggested high-level scenarios for BAT testers to cover (e.g. Create a store event, cancel a store event, search for store events at XX branch).
- Agree upon these scenarios and prioritise them. Some scenarios may be more important than others
- Once the feature is ready for Business Acceptance Testing, reach out to the BAT tester(s)
- Check to see what information they currently have of the feature, is an overview of the feature needed?
- Share suggested scenarios for them to follow along with a list of questions to elicit feedback
- Ask if there are any other scenarios you think should be covered or will be used once it goes live?
- Is there anything that concerns them?
- Are they happy for the feature to go live?
- Provide them with a clear channel on how to communicate this feedback (specific person)
- Provide them with information we need from them if they find bugs
What they did
What did you expect to happen?
What actually happened?
** User credentials
For some extra context:
The company is in multiple countries and they want business users from those countries to try out the features and see what they think. But it’s only typically 1 person in each country doing the BAT.
Over to you
Is testing software in this way something you have experience with? What process have you used in the past or are you currently using? What advice can you give to manage this business acceptance testing?