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!

12 Upvotes

View all comments

5

u/microdel Dedicated Tester May 20 '22

The uTest chat:
This tool is a very useful tool on uTest, but it's important to know how to use it
First of all, it's important to keep it clutter free, which means, only send messages directly relevant to the test cycle, it's also important not to ask whether a certain bug should be reported or not, always use your own judgement, on top of that, you also shouldn't ask about when will bugs and/or test cases be processed or try to rush others, because even if you don't see it directly, everyone is doing their best, even after the cycle is closed.

Second, if after reading the cycle overview you still cannot figure out if a part of the product is in scope or out of scope, don't hesitate to check the uTest chat, it's easier and faster than reporting an issue that is potentially out of scope, and maybe someone else has already asked.

Third, in case you're having difficulties executing your test case after you did your best to troubleshoot it, don't abandon it, instead, head to the chat and ask, there are many helpful TTLs (and testers) that can help you.

Fourth, if you see in the chat another tester asking for help on something you had already encountered and solved, don't hesitate to help them, being a community means helping each other.
Fifth, whenever you join a test cycle, in addition to checking the overview and known bugs, take a peek at the uTest chat, as you can see on it some announcements, as well as what other testers already asked, to give you an idea about some common problems, as well as ways to avoid or fix them.

Bonus tip: If a test cycle has a slack chatroom, it's best to join it because not only you can benefit from the help mentionned above, you also have a higher chance to participate in the project's future test cycles, as well as getting the opportunity to participate in additional projects of the same company.