Originally posted by Jules:
When we include screenshots we also include a small passage to explain that they are a guide only and that the final appearance of the actual screens may differ.
Sometimes clients employ inexperienced UAT testers from the ranks of their admin and support staff.
It then becomes a right pain in the derry when they decide that they are going to prove their worth by raising every little descrepancy between screenshot and system as a bug!
We just went through this same situation. We had screen shots in the Specification document and of course the final web pages were a lot different! Some bugs did get reported because of it.
I think that screen shots are ok at this level *as guidelines only*. At least they will give you some kind of visualization for writing test cases and such.
But to actually test against them is not a good idea. They are too high level at this point in the process.
[This message has been edited by kMcLeod (edited 10-11-2001).]