Testing Guidelines For Junior Tester

This is a very short visual guide for a junior tester.

screen-shot-2017-01-21-at-09-54-08

Do exploratory testing. That means: be curious, attentive and organized.

come1   come2

Try mindmaps to get the testing ideas and cheatsheets to try different inputs and watch carefully for side effects.

screen-shot-2017-01-21-at-09-44-25

Trust your intuition, see what others do not see and make it visible. How? Use different personas, ask strange questions, like: “can this application kill a person”, and read stories how others test.

screen-shot-2017-01-21-at-09-53-16

Report findings properly, describe the beauty harm in simple reproducible steps and do not forget to mention, why it is important to fix the bug in next iteration. I think it is bad style to write in bug report something like this: “unless you remove the “border=0” attribute“. Show respect = get respect.

 

Enjoy the video, which inspired me to write the guidelines:

 

 

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s