Acceptance testing is the final phase in any systems development project. It comes after the product or solution has been developed and (hopefully) tested thoroughly by its creator. The purpose of acceptance testing is to ensure that the requirements are met.
At this point, it’s up to the client to verify that the system lives up to the agreed-upon specifications, as well as any implicit or expected requirements. Here are eight guidelines to follow when running your own acceptance testing sessions.
1) Requirements will Change
Requirements will change—this is a gospel truth. Formulate a strategy and establish a process for dealing with changing requirements. The process you...read more
By Ulf Eriksson
Accomplished, self-reliant creative industry ninja for well over a decade, with a solid knowledge and insight to a wide range of web/UX and creative skills.
I have high expectations for the results of my labour. I am confident in my ability to produce, and while I prepare for the worst, I do the work necessary to tilt the odds so that the best will happen.
Lifelong design & media industry geek. Ardent traveller. Relentless optimist. Fanatical gamer.
