How to write user acceptance testing for web app?
I need some guidance around user acceptance testing cases for web development, meaning I have developed GUI for a user to log in and register. I need now to write test cases for this graphic user interface for a client. Anyone who can help me to do this? I am a cloud stack developer and full-stack, so my experience to quality assurance is quite limited but I am open to knowledge and learn as well.
For starters, don't pass to your client the impression that you can document all your testing, because testing is a performance, not artifact generation. It is made of both explicit and tacit knowledge, including tacit oracles, which can't be described down.
Now, changing the question to "how to communicate the information I've uncovered during testing?":
- Easiest and more complete way: Record your testing and express your thinking process along the way. This is known as Testopsy;
- You can fill out a charter of your testing sessions (possible template here), followed by debriefing session;
- You can pair with your client during your testing;
- You can describe specific actions and outcomes in sequential order, attempting to encode all the thought process you had during your testing.
Speaking of the last point, unless your context really calls for this type of solution, I would suggest to not go this way. If the idea of encoding a human thought process doesn't seem absurd and misleading to you, I would suggest reading this blog post series.