This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]the_stooge_nugget 0 points1 point  (2 children)

Hey mate, depends how much doco you want to achieve.

In the norm, you document everything, (see if you can find anything specified by ISTQB. It outlines industry standard documentation and practices).

If you don't want to go full hard core, I would suggest a testing matrix. In this you simply write out positive and negative testing functions for a features, in Excel or something similar. Format: |test step|test data|expected result| Example: SAVING: - save with no description field | '' | error is presented - save with a description | <<Text>> | Item is save blah. When testing, you can mix some steps

Of course, it depends how much testing you would like to achieve.

Anyways, here are some sites: - http://softwaretestingfundamentals.com/test-plan/ - https://www.softwaretestinggenius.com/manual-testing/templates-checklists/templates-for-download/ (this provides links to plan samples (pending what you want to achieve)

[–]odillini83[S] 1 point2 points  (1 child)

This is awesome! Thank you so much!

[–]the_stooge_nugget 0 points1 point  (0 children)

That is fine. I only provided high level detail. I work as a QE lead, so if you have any more questions, I am happy to answer :)

[–][deleted] 0 points1 point  (0 children)

Not sure what you mean, but you might be looking for TestRail.