Weekly overview of the bug-hunting category- week 27, 2019

in #utopian-io2 years ago

This is a report on the weekly contributions to the bug hunting category. The post contains basic stats like the number of contributions received by the category, an excerpt on new contributors if there are any and a detailed comparison of the week's output with previous weeks.

utopian (1).jpg

Previous Reports

2018
2019

Bug hunting contributions summary

Week 27: June 27th - July 4th
  • 33 Contributions, 31 scored higher than 0
  • An average score of 66.87
  • 12 unique contributors
  • No Staff Picks
  • No new contributors

Number of reviewed and rewarded contributions

image.png

Average score

image.png

Reports Reviewed By Reviewer

image.png

image.png

This week the numbers increased from what we had in the previous week. In total there were 33 contributions reviewed. That is 4 more contributions than we had last week. There were 2 reports that were not scored. The reasons were:

  • The contributor in this case (1)conducted the test by playing songs that did not have genres defined in the metadata.
  • The other case was ignored for being irrelevant and completely lacking, of the standards that define a bug report.

That left us with 31 contributions eligible for rewards. This brought the average to 66.87, greater than last week's average of 62.25. While we were still basking in joy from last week's increase in average, we get another high turn out. We are hoping this run continues. There were more crash cases than we had in the previous week.

The week like the week before, had quality outputs. Much kudos to the contributors.

contributions

With 33 contributions this week, @ammarraisafti and @asad44 tied the spot for top contributor of the week. Both had the most input of 6 reports apiece. Of the combined 12 reports, 11 were scored, 6 were scored 70 or higher. In total, @asad44 received an average score of 67.9 while @ammarrraisafti scored 69.5. The remaining contributions were thinly sparsed between the other hunters.

After 5 weeks as the most active repo, ACG loses its top spot to GrowTracker . This project received 6 reports

This app was created to help record data about growing plants in order to monitor the growing conditions to help make the plants grow better, and identify potential issues during the grow process.

You can look up the repo by following this link - https://github.com/7LPdWcaW/GrowTracker-Android.

Other project repos that stood out

If you are looking for new applications to explore, here are some repos that stood out this week.

And there you have it. Happy hunting :D

Common Mistakes And How To Fix Them

I will be highlighting the common mistakes found this week. I will also be offering tips on how to avoid them in future contributions. The tips will depend solely on the scores received by the contributions in a particular week.

1. Contributions with a score below 40

The severity level of the bug was marked as negligible.

Submission of cosmetic or trivial UI issues (phone orientation, phone locking/unlocking etc.) that have a negligible effect on the functionality of the application may lead to a lower score of your contribution, thus reducing your chances of receiving a reward

  • If what you spotted is a discrepancy in the user interface or just the front end appearance of the software, then it is most probably a trivial bug and would be scored as such. So make sure to look out for this.

  • Also, there are times when a contribution is scored negligible because the expected behavior of a particular feature could still be achieved by a default option. For example - while some third party camera apps may not work when used for uploading within other applications (probably because the PATH for that particular cam app is not set), the default android cam works. It will be particularly stressful and redundant to have the project owner set a unique PATH for every cam application out there. This is one thing a contributor should look out for.

2. Contributions with a score below 60

The contributor made no efforts to pinpoint the cause, or applied incorrect methods in searching for it.

  • To avoid being scored in the questionnaire with this option, I will advise hunters to comb through the app's repo. Search the repo using a keyword related to the affected feature, it could be the name of the function itself. If found, analyze the block of code behind the function's implementation. Check for syntax and logical errors, document your findings.

  • You can attach logcats in your reports for issues that involve a crash. If you don't know to produce one, watch this tutorial for how to.

Other News


This is to inform contributors and the general public that while reports will be accepted to projects outside the whitelist, they will only be reviewed if the issue opened is acknowledged by the project owner or maintainer.

While the new guidelines are yet to be officially announced, bug-hunters and open source enthusiasts looking to help open source projects, please take a look at our whitelist of projects that you can submit bug reports for:

https://docs.google.com/spreadsheets/d/1S7ayFTEy5CBMyeJvFRgq5JUjlqZxFjWAWhhrBL0GC60/edit#gid=1954068373


If you wish to have your open source projects added to our whitelist you can contact us on our help channel at our discord server. You can also leave your questions and comments below :)


Thanks

@fego

Sort:  

Hello, @fego!

Thank you for taking the time to provide another detailed report. It is great to see that you have many active contributors providing quality material for the category, and I hope to see more of the same in the following weeks. As always, your report is comprehensive and well-illustrated with relevant graphics. Keep up the good work.

Once again, you managed to compose an extensive report that includes all the necessary details, and even contains useful tips for contributors. It is good to see that quality standards are kept high, and I appreciate the time and effort you put into your work.

Have a great week ahead, and see you next week.

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.


Need help? Chat with us on Discord.

[utopian-moderator]

Thank you for your review, @lordneroo! Keep up the good work!

Hi @fego!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server

Congratulations @fego! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

You distributed more than 5000 upvotes. Your next target is to reach 6000 upvotes.

You can view your badges on your Steem Board and compare to others on the Steem Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

To support your work, I also upvoted your post!

Vote for @Steemitboard as a witness to get one more award and increased upvotes!

@fego You have received a 100% upvote from @botreporter because this post did not use any bidbots and you have not used bidbots in the last 30 days!

Upvoting this comment will help keep this service running.

Hey, @fego!

Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!

Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).

Want to chat? Join us on Discord https://discord.gg/h52nFrV.

Vote for Utopian Witness!