Weekly overview of the bug-hunting category- week 65, 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

2018

2019

Bug hunting contributions summary

Week 65: March 21st - March 28th

17 Contributions, 17 scored higher than 0
An average score of 57.5
8 unique contributors
No Staff Pick
2 new contributors - @sagirahmed, @jga

The contributions

Contributor	URL	Project	Reviewer	Score
@rivalzzz	steem-keychain-footer-isn-t-sticky	steem-keychain	fego	48
@harry-heightz	unable-to-load-contents-of-a-post-gotten-from-a-search-result-of-words	esteem mobile	fego	48
@harry-heightz	search-on-the-the-list-of-people-im-following-doesnt-work-it-is-unresponsive	esteem mobile	fego	48
@harry-heightz	the-app-crashed-when-i-scrolled-on-the-commentsreplies-page	insteem	tobias-g	85
@harry-heightz	app-crashes-when-i-click-on-the-icon-to-check-voters-info-or-the-reply-button-this-crash-happens-after-i-search-a-word-and-open-one-of-the-search-results)	esteem mobile	fego	88
@harry-heightz	unable-to-get-past-startup-screen-when-i-try-to-check-out-a-mention-notification	esteem mobile	fego	57
@tony-duke	no-action-is-taken-when-i-click-on-a-tag-on-esteem-mobile-app-v2-1553147311856	esteem mobile	fego	57
@horpey	clicking-on-transferred-notification-opens-user-s-feed-without-bottom-menus	esteem mobile	fego	57
@sagorahmed	player-is-crashing-when-i-remove-a-song-and-click-on-track-changer-next-previous-button	bop music player	fego	60
@sagorahmed	unable-able-to-play-songs-form-file-manager	bop music player	fego	57.5
@harry-heightz	app-freezes-when-i-enable-shuffle-and-try-to-play-next-track-on-an-album-with-just-one-song-in-it	bop music player	fego	48
@jga	steem-blockchain-freezes-if-the-sbd-supply-is-0	steem blockchain	fego	90
@ahyar92	the-application-crashes-and-cannot-be-used-again-when-playing-music-files-that-have-been-deleted	bop music player	fego	60
@ckole	couldn-t-edit-comment-initial-comment-replaced	esteem mobile	fego	42.5
@tony-duke	no-feedback-after-the-mute-action	esteem mobile	fego	42.5
@tony-duke	the-message-icon-on-post-cover-not-responding	esteem mobile	fego	34.5
@horpey	bullet-shortcut-and-headings-place-cursor-at-the-back-of-the-first-letter-in-the-editor	esteem mobiile	fego	54.5

In the last week, we had 17 contributions to the bug-hunting category at utopian-io. There There no staff picks. All 17 of the contributions were scored above 0.

The highest scored contribution was by a new contributor - @jga. He observed that when the SBD supply is 0 the witnesses stop producing blocks. You can read the details of this report in full here.

Weekly Average Score and number of Contributions

Chart breakdown:

The average score for this week is 57.5
This week's average is higher than the 4-week average of 56.10 by 1.4.
It is higher than last week's average of 57.41

Hunter Totals and Average

- This week we had 8 unique contributors, 2 more than the number we had last week - There were 6 reports from @harry-heightz, 3 from @tony-duke and 2 from @horpey and @sagorahmed. 1 each from the other 4 contributors. - @harry-heightz is presently the category's top contributor with 31 finds. That is 31 finds since the start of the year. - @blockchainstudio has a 4 week average of 82.33, making him the contributor with the highest average score. - 5 of the contributions were scored higher than the week's average

Reports Reviewed By Reviewer

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

Average review scores in the past 4 weeks

@fego has reviewed 36 contributions with an average score of 53.6.
@tobias-g has reviewed 11 contributions with an average score of 59.60.

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 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