Wendy – why are you worried about this?
One of the biggest issues we ran into during our Unified Communications project was the development of test scripts.
As you are implementing your learning ecosystem, chances are you will be asked to create test scripts. Or at least participate in that process.
Spending time defining testable requirements (as much as possible at this point) will save time later on.
Like…when you are also trying to develop training materials and prep for go-live.
In Wendy’s Utopian Fantasyland:
- Test scripts are based on requirements.
- The requirements are based on what the user needs to be able to do.
- And we wind up with a system that works for humans.
Test scripts should have two levels:
- Functional – do the buttons work
- Most test scripts focus on the functional
- IT folks will focus on this.
- Functional testing is useful TO A POINT!
- Procedural – can someone actually complete a task
- All of the buttons can work and it passes the functional test, but if you try to walk through a series of steps – you can’t complete the task.
- When I see solutions fail, it is because they tested whether the individual buttons work but didn’t bother to walk through what humans actually do when they use the tool.
- I haven’t seen a solution yet where I push just one button to perform a task.
Not all requirements have testable components.
Some are just “does it exist – yes/no”.
So I figured it would be easier to identify what could be tested and what couldn’t up front.
You may need an IT friend, or two for this.
How I’m approaching this (moving forward, because I learned my lesson) is explained in the video below.