This blog post applies to SharePoint as well as any custom software your write. This is the high level user acceptance testing that should be done when finishing a every custom project you do.
- Write User Scenarios/Requirements
- Develop Code based on requirements
- Create a test plan, which is all of the tests your will document and run
- Write test cases based on the requirements and user interface
- Run test cases to make sure everything is working
- (optional) Use a subset of tests as a smoke test
Feel free to debate, suggest or recommend any changes to the steps.
Here is what the testing process might look like.
- Go to the folder location where you have stored the testing documents such as http://<sharepointsite>/<project name>/Testing/UserTests
- Open a testing document such as 01-UserTests-<component>.docx
- Record results in a new Test Run document with name [test##]-[YYYYMMDD]-[user]-testresults.xlsx (example: 01-20100610-bschwartz-testresults.docx)
- Run through every test in testing document and put Pass/Fail and the time it took to run the test in a common location which might just be a spreadsheet, database or formal tool.
- Update Feature spreadsheet as components pass the user testing
Here are some example files you could use to get started.