Weekly overview of the bug-hunting category- week 60/61, 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 60: February 14th-20th

9 Contributions, 7 scored higher than 0
An average score of 52.79
4 unique contributors
No Staff Pick

Week 61: February 21st-27th

18 Contributions, 18 scored higher than 0
An average score of 51.64
5 unique contributors
No Staff Pick

The contributions

Week 60

Contributor	URL	Project	Score
@blockchainstudio	busy-2-5-6-deleted-post-loading-reward-balance-refresh	busy-2-5-6	80
@horpey	powering up steem transferring steem to savings give error and blank page	esteemsurfer	57
@horpey	esteem-mobile-reply-doesn-t-save-text-in-local-storage	esteem-mobile	45
@vishalsingh4997	buttons-are-not-working-utopian-io-mobile	utopian-io	0
@horpey	esteem-mobile-tag-bottom-borders-are-cut	eSteem v2	38
@horpey	esteem-mobile-centered-images-not-fit-in	esteem v2	44.5
@horpey	favourite-list-doesn-t-display-user-s-avarta	esteem v2	48
@horpey	weird-space-after-html-heading-and-the-next-words	esteem-v2	57
@face2face	features-within-post-dropdown-are-not-working-properly	esteem-v2	0

Week 61

Contributor	URL	Project	Score
@harry-heightz	weird-home-navigation-issue	knacksteem	48
@harry-heightz	incorrect-or-absurd-date-showing-on-a-newly-published-article	knacksteem	48
@harry-heightz	steemit-links-contained-in-a-post-are-tampered-with-when-the-article-is-published-via-knacksteem	knacksteem	57
@harry-heightz	the-app-crashed-after-i-tried-to-view-the-favorites-page-after-adding-an-author-as-favorite	steemer-v-147	80
@tony-duke	the-follow-button-in-steemblr-not-functioning	steemblr	41
@harry-heightz	the-app-crashed-after-nonce-was-set-to-1-trillion	steem-v-147	51
@blockchainstudio	cannot-edit-posts-user-page-loading-fail	busy.org	77
@harry-heightz	knacksteem-automatic-redirection-to-steemit-when-a-user-profile-was-searched-and-clicked	knacksteem	45
@tobias-g	fixed-footer-prevents-post-trade-call-to-action-from-being-clickable	swapsteem	68
@tobias-g	account-holder-name-value-bound-to-same-data-as-swiftbic-code	swapsteem	60
@riyandacountri	find-bugs-in-the-application-bob-music-player-when-accessing-equalizer-settings-in-landscape-mode	bob-music-player	24.5
@tobias-g	search-value-of--or-an-empty-value-causes-blank-page-upon-search	steemblr	48
@harry-heightz	using-the-voting-slider-on-mobile-device-causes-the-web-page-to-lose-fitted-to-display-optimization	knacksteem	31
@blockchainstudio	user-page-loading-fail-page-not-found	busy.org	70
@harry-heightz	the-category-tag-on-post-previews-exhibit-a-weird-behaviour	knacksteem	48
@harry-heightz	the-whole-page-clears-out-and-becomes-blank-white-when-i-click-on-the-upvote-or-downvote-button	knacksteem	45
@harry-heightz	mobile-android-app-absurd-profile-behavior	esteem-v2	45
@harry-heightz	if-all-texts-on-post-editor-is-cleared-on-steemit-side-by-side-view-becomes-nonexistent-post-editor-reverts-to-default-steemit-view	steemplus-v-37	43

In the past two weeks, we have had 27 contributions to the bug-hunting category at utopian-io. There were no staff picks. Approximately 30% of the contributions were scored higher than the 4-week average for both weeks.

The highest scored contributions were by @blockchainstudio and @harry-heightz. Harry_heightz reported a crash while Blockchainstudio found a bug on the busy.org wallet and reported it. He observed that :

If the claimable balances in the wallet are claimed externally, then even if a user clicks the "Claim rewards" button, it only tries to re-claim but doesn't update anything.

Weekly Average Score and number of Contributions

Chart breakdown:

The average score in the last two weeks were 52.79 and 51.64 for weeks 60 and 61 respectively.
The average from each week is lower than the 4 week average of 53.61
There were 6 reports each from @horpey in week 60 and 11 reports from @harry-heightz in week 61.
@horpey is still the category's top contributor with 18 finds. That is 18 finds since the start of the year, he's closely followed by @harry-heightz with 15
Approximately 30% of the contributions were scored higher than the 4-week average

Reports Reviewed By Reviewer

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

Average review scores in the past 4 weeks

@fego has reviewed 28 contributions with an average score of 53.21.
@tobias-g has reviewed 13 contributions with an average score of 54.46.

Common Mistakes And How To Fix Them

I will be highlighting the common mistakes found this last two weeks, 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 issue you reported is OS related and is therefore not the application's fault. The operating system does not support this particular feature

My advice for cases like this is - 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 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.

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