End-user accpetance testing/test plan
Posted: Thu Mar 25, 2010 8:16 am
My manager wants me to produce a document to assist her and other stakeholders in validating the system does what it is supposed to do, from a user perspective.
Basically a step by step document for thouroughly testing each module/component of the system, from an end-user perspective, validating messages, workflow, etc.
My questions:
1. Are there any tools to assist users in automating this process somewhat? Maybe an events recorder in FireFox like iMacros? Visual validation is still required, so atuomation is impossible(unpractical). Making sure windows are the correct size, drag and drop works, etc.
2. I test thouroughly at this level as well, just as part of my development process and one issue I have is easily testing the various user level restrictions/constraints/etc. I have a engineer user, an inspector user and super admin user, each with different access rights.
3. Any examples of what a test plan of this type might look like would probalby be helpful for me. Currently I have a simple notepad document indicating the steps and expected results of carrying out an action, such as adding a repair document
I currently expedite the process by having three browsers open (IE: I login as engineer user, FF: I login as inspector user, OP: I login as super admin user).
IE is our intranet browser of choice, so I wonder if there is a way to open distinct tabs with individual session cookies???
Somethinglike this:
http://www.klariti.com/templates/Accept ... late.shtml
http://www.contractedwork.com/pport/p12939/UATTEMPL.DOC
A template which I can follow in building our own internal user acceptance test plan.
Most important is an easy to follow sequence of steps which end-users can follow to ensure the system acts as expected.
Cheers,
Alex
Basically a step by step document for thouroughly testing each module/component of the system, from an end-user perspective, validating messages, workflow, etc.
My questions:
1. Are there any tools to assist users in automating this process somewhat? Maybe an events recorder in FireFox like iMacros? Visual validation is still required, so atuomation is impossible(unpractical). Making sure windows are the correct size, drag and drop works, etc.
2. I test thouroughly at this level as well, just as part of my development process and one issue I have is easily testing the various user level restrictions/constraints/etc. I have a engineer user, an inspector user and super admin user, each with different access rights.
3. Any examples of what a test plan of this type might look like would probalby be helpful for me. Currently I have a simple notepad document indicating the steps and expected results of carrying out an action, such as adding a repair document
I currently expedite the process by having three browsers open (IE: I login as engineer user, FF: I login as inspector user, OP: I login as super admin user).
IE is our intranet browser of choice, so I wonder if there is a way to open distinct tabs with individual session cookies???
Somethinglike this:
http://www.klariti.com/templates/Accept ... late.shtml
http://www.contractedwork.com/pport/p12939/UATTEMPL.DOC
A template which I can follow in building our own internal user acceptance test plan.
Most important is an easy to follow sequence of steps which end-users can follow to ensure the system acts as expected.
Cheers,
Alex