Hello,
I think your question is more about what documentation works well, but the answer lies more in getting to know the humans who are doing the testing. (I agree with the previous poster - do the testers have time to work on their own, and how many details do they need?)
With some clients, I can ask them to select a few examples from regular daily work using the new methods, new workflow, and new reports.
With other clients, I meet them and step through the process of testing a few examples from regular daily work and we try out new procedures and new reports together.
In both cases I keep testing steps brief - for example, “Enter and release a Bill.” (Not field by field instructions → field by field should not be needed; test subjects should be the strongest users of the group.)
When a client indicates they can test on their own versus another meeting…
- Ask how much time they need.
- Advise them, “I can see whether you signed into our test area.” 😄
- Agree to “Check back in” (as many days as they said they needed).
- Put a reminder in your calendar.
- Later, check to see who signed in, what screens were opened, and ask the client for the results of their testing (or do they need more time?).
- If they test and find a problem, you’ll hear from them long before the reminder arrives on the calendar. If they forget to test or can’t find the time, make an appointment to test together with them when the reminder arrives.
Laura