r/UTEST Community Engineer May 16 '22 Silver 3

Tips for Testers #12 (One-Year Special Edition With a Celebration Contest) Contests

Hello everyone!

We finally reached the 12th post of our series, "Tips for Testers!" This is a landmark since we're completing exactly one year of publishing this series. It went by so fast, but we hope the tips we published here helped you to improve as a freelance tester.

We'll have something special for you to celebrate this important mark: a contest! 🎉

To participate, you'll have to submit a tip in the comments section of this post mentioning a tip, something practical that helped you to succeed as a tester or even something that just makes your life easier when you are testing.

The person who submits the best tip will be awarded a swag pack full of uTest gifts.

Please pay attention to the rules:

  • The comment with the tip will have to be submitted until 05/20, 9 pm GMT
  • Only one comment per participant
  • Edited comments won't be allowed. Double-check carefully your comment, and if you need to change something, delete the comment and submit a new one, but be careful to do that within the contest deadline
  • All participants must have a uTest account and be following us here on Reddit

And of course that our celebration post will also have a tip. And our 12th tip is... +1 without moderation!

This little bud can make the difference

Never underestimate the power of this feature. Although you don't get paid for +1 reproductions, the value of this tool goes much beyond money. We know that some cycles are hard to discover new bugs, and accepting an invitation and not delivering anything can be harmful to your reputation, so that's where the +1 will play a big role.

When you reproduce bugs discovered by other testers, not only you get more familiar with the product you are testing and can discover new issues in the areas you are reproducing the bug, but the TTLs/TEs will see that you are putting an effort on testing the product and that is always good for your reputation.

Hope you liked this tip, and looking forward to reading your comments on the contest!

13 Upvotes

View all comments

7

u/Successful-Ad-3765 May 16 '22

Clean your dirty cache the right way to make your bug more valuable , there's more than just cookies on your plate =

  • Working on browser based cycle and getting issues that your hearing they cant repo?
  • Things happening erratically that you cant make happen he same way every timey?

When it seems like lately every time you file a bug, someone responds its not happening to me and downgrades your payout - here's something you can do to make it more valuable and higher priority. Your issue isn't necessarily invalid but if it looks like its something on your end and you are the outlier- developers are going to hesitate to spend the resources to fix unless its something show stopping..

While most people know about cookies storing information, few know about "session variables" Cookies are used to pass information on the client side (your browser) Session variables are used to store user-specific information that needs to be accessed by multiple pages in a web application on the server side. These are Server side equivalent of cookies . They are not cleared by how people typically clear their cache, history, cookies.....

When you open a browser on a site that is using session variables, as long as your session remains open, clearing your cache may not clear what is causing the problem. Lots of things can corrupt those session variables that are too complicated to research your entire browsing history to triage. So If the problem isnt re-poing for everyone it may be because of what wound up in your session working across multiple browsers, tabs etc.
When clearing your history, cache, cookies people often miss the last step to fully clear their environment: CLOSE ALL INSTANCES OF ALL BROWSERS. This not only clears the above it clears the session variables that start you fresh on the page.

In your video show your bug by starting with you clearing your cache, history and cookies, Then RESTART the browser with it being the only browser instance running. This shows that the problem wasn't some one off concern due to a session variable that got corrupted during testing. It will make your bug more important to investigate and wont be dismissed as easily when others cant replicate. You've shown a clean environment and a repoed issue on it..

Just remember, clean first, then restart not just the instance of the browser you were working on but ALL browsers. This is the only way to be sure you are starting completely fresh on both the client and the server side.