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

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

Bug hunting contributions summary

Week 58: January 31st - February 7th
9 Contributions, 8 scored higher than 0
An average score of 55.75
8 unique contributors

The contributions

Contributor	URL	Project	Score
@stmdev	hivemind-inconsistent-reputation-representation	steemit/hivemind	60
@harry-heightz	opening-notification-should-take-user-directly-to-content-they-are-being-notified-about	eSteem v2	38
@stmdev	beem-0-20-17-blockchain-stream-block-fail-with-only-ops-true-on-blocks-without-ops	beem v2	80
@aafeng	cannot-see-voters-count-for-some-posts	steemit/condenser	30
@blockchainstudio	comments-tab-and-delegation-detail-don-t-work-etc	eSteem v2	85
@tdre	creating-a-poll-with-lengthy-answer-encounters-500-response	dpoll	48
@nawab69	actifit-can-t-run-in-my-device	actifit	0
@horpey	favouriteicondoesnotindicateusersalreadyonthelist	eSteem v2	45
@tobias-g	unable-to-load-swapsteem-via-https-resolved	swapsteem	60

This week we had 9 contributions, 6 less than we did last week. The esteem app is still the project with the most contributions. This week it received 3 of the 9 contributions.

8 of the 9 reports were scored higher than 0.

The highest scored contribution was by @blockchainstudio, his report was a collection of 5 bugs affecting eSteem Surfer 2.0.5. There was also a contribution from @stmdev to the beem project that was scored high as well, he had noticed :

blockchain.stream(start, stop, only_ops=True) and Block(blocknum, only_ops=True) fail with a BlockDoesNotExistsException if the block contains no operations.

Weekly Average Score and number of Contributions

Chart breakdown:

The average score this week is 55.75
The average score is approximately 10.5% higher than the 4 week average of 49.87.
This week's average is higher than the 4-week average by 5.88.
It is higher than last week's average of 43.75 by 12, that is 21.5% higher. Overall we can say that the quality of contributions increased this week.

Hunter Totals and Average

This week we had 8 unique contributors, 2 less than last week
There were 2 reports by a single contributor, @stmdev. 1 each from the other 7.
@horpey is still the category's top contributor with 12 finds. That is 12 finds since the start of the new year, he's closely followed by @blockchainstudio with 11
Approximately 44% of the contributions were scored higher than the week's average

Reports Reviewed By Reviewer

The category has received 61 contributions this year, 2019. 56 were rewarded and scored higher than 0. However, in the past 4 weeks there were 49 bug reports scored higher than 0. These 49 were assessed by 2 reviewers.

Average review scores in the past 4 weeks

@fego has reviewed 34 contributions with an average score of 50.34.
@tobias-g has reviewed 15 contributions with an average score of 48.8.

Common Mistakes And How To Fix Them

I will be highlighting the common mistakes found this week, and I will 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 scored 0

The feature is intended and is not a bug.

My advice here is - if you are not sure it's a bug, then wait for the PO to affirm your observations. I know most times the project owners are too busy and do not respond in reasonable time and so you are pushed to post on utopian without them first acknowledging whether an observed behavior is a bug or an intended. It can be frustrating but I'd still advise that hunters in the future should wait for the PO's thoughts, especially in cases where the details behind the implementation in question are sketchy.

2. Contributions with a score below 40

The title provided sufficient information, but the description of the steps to bug reproduction severely lacked in clarity..

To avoid being scored with this option in the questionnaire, contributors are advised to always include sufficient detail to reproduce the bug, as well as screenshots, video recordings or animated GIFs if they help to describe and identify the reported bug. These details should be within the context of the bug. Recording or documenting steps that are irrelevant to the bug will affect your score.

Other News

While the new guidelines are yet to be implemented, 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