- Customer Success should Prepare/Review test cases based on Requirement Gatherings session (FD if available)
- Customer Success/Trainer should test them 3 days before Customer training & sort the issues with Dev Team
- Test cases should be organized in such a way to help flow in training
- The primary focus of UAT is TRAINING. Users can give their suggestions to us via Project manager/coordinator
- Training Format: Hands-on. You do a transaction and let them do one. This way they can learn things faster
- Key users questions usually fall on 3 categories a) How to use the system? b) Scenarios c) Why this way or why I have to do in multiple screens? Show thing for (a ) & (b) and education/justify for (c)
- Record Transaction references in test case document
- Get Signoff. If they object, Get it with Comments
- Support test cases with prints & reports if any
- If something is not working, move on to the next saying we will come back. Don't panic. Inform Team over chat
- After the session, Track bugs and suggestions in a tracker (sheets or asana) liaise with Dev team for completion