Test Guidelines

Application Change Management Protocol for Testing Phase

Superuser resource requirements for testing:

1) # Providers 1 assuming standardization plus if there is a specialty or practice that has workflow(s) specific to that specialty or practice they should send a provider to test them An alternative would be to have a core team member demonstrate the workflow for the provider but that would probably take almost as much of the provider’s time.

2) # and type of other users 1 per role plus if there is a specialty or practice that has workflow(s) specific to that specialty or practice they should send a superuser to test them For 1 and 2 above: These minimums are absolutely critical in order to ensure that the documented workflows actually cover all the critical details of all practices and specialties. The superusers and providers will be asked not to just test the documented workflow but to try anything they do that is not covered by the documented workflow.

3) Total duration they will be needed for 4 hours per day for 2-3 days total

4) # hours per day They do not have to test every day, the number of hours will depend on how many roles and workflows they test. I would say 4 hours on the days they are needed for testing. Generally they would test for 1 or 2 days near the beginning of the testing period as part of the 1st or 2nd testing cycle and then possibly be asked back a week or so later to retest if significant changes are made to the config or workflow.

This testing time will also provide additional training for those involved and increase organizational acceptance.

For more information, please see: Enterprise Test Strategy