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

Previous Reports

• Weekly overview of the bug-hunting category- week 44, 2018
• Weekly overview of the bug-hunting category- week 45, 2018
• Weekly overview of the bug-hunting category- week 46, 2018
• Weekly overview of the bug-hunting category- week 47, 2018
• Weekly overview of the bug-hunting category- week 48, 2018
• Weekly overview of the bug-hunting category- week 49, 2018
• Weekly overview of the bug-hunting category- week 50, 2018
• Weekly overview of the bug-hunting category- week 51, 2018
• Weekly overview of the bug-hunting category- week 52, 2018
• Weekly overview of the bug-hunting category- week 53, 2018
• Weekly overview of the bug-hunting category- week 54, 2019
• Weekly overview of the bug-hunting category- week 55, 2019

Bug hunting contributions summary

• Week 56: January 17th - January 24th.
• 11 Contributions, 11 scored higher than 0.
• An average score of 50.91.
• 8 unique contributors.

The contributions

Contributor	URL	Project	Score
@louis88	esteem-mobile-206---app-crash-when-claiming-rewards	esteem V2	45
@blockchainstudio	inconsistent-reputation-score	esteem V2	65
@syedumair	posts-under-active-votes-and-children-category-are-not-displayed-right-away-until-we-change-servers-and-restart-esteem-v2-app-v2-0-6	busy.org	45
@tobias-g	esteem-mobile-206---voter-info-doesnt-sort-after-first-use	esteem V2	60
@horpey	esteemsurfer204 - does not support links without https prefix	esteem surfer	45
@face2face	unable-to-see-images-of-blog-in-esteem-v2-0-6-if-post-created-by-busy-interface	esteem V2	41.5
@louis88	esteem-mobile-206-bug-steemconnect-login-error---username-with-a-dot-in-the-name	esteem V2	54.5
@louis88	esteem-mobile-206-bug-incorrect-markdown-cursor-position-on-bold-and-italic-text-in-editor	esteem V2	57
@rufans	esteem-mobile-v2-v2-0-6-an-account-estimated-balance-isn-t-displaying	esteem V2	43
@syedumair	esteemapp-v2-2-0-6-crashes-upon-re-opening-after-setting-the-server-to-https-steemd-privex-io-and-closing-the-app	esteem V2	69
@peerzadazeeshan	esteem-app-is-not-able-to-upload-image-capturing-through-picsart	esteem V2	35

This week we had 11 contributions, 9 less than we did last week. And as with the previous week, a majority of the reports were submitted to the project repository of eSteem mobile V2.

All 11 reports were scored higher than 0.

The highest scored contributions were by @tobias-g and @blockchainstudio. Tobias while testing esteem V2 found that :

The voter info table does not sort after the first use, you have the ability to sort the table once, however, when a user attempts to sort again, this does not work.

The table data shown in the voter info pages should reflect the sort method chosen by a user.

Blockchainstudio reported the incorrect reputation score displayed on a user's profile when viewed on the busy frontend. He spotted two unique unexpected behaviors:

• Reputation score is rounded
• Reputation scores in user info and post are different.

You can get more details on the bug, what led to it and how it was fixed by checking this link - https://steemit.com/utopian-io/@blockchainstudio/inconsistent-reputation-score.

Weekly Average Score and number of Contributions

Chart breakdown:

• The average score this week is 50.91
• The average score is approximately 3% lower than the 3 week average of 52.39.
• This week's average is lower than the 3-week average by 1.48.
• It is higher than last week's average of 50.39 by 0.52, that is 1% higher.

Hunter Totals and Average

.

• This week we had 8 unique contributors.
• There were 3 reports by a single contributor, @louis88. 2 reports from @syedumair and 1 each from the remaining 6 hunters.
• @horpey is still the category's top contributor with 10 finds. That is 10 finds since the start of the new year, he's closely followed by @blockchainstudio with 8.
• 25% of the contributors had average scores that were higher than the 3-week average of 52.39.

Reports Reviewed By Reviewer

The category has received 37 contributions this year, 2019. The contributions received by the category in the past 3 weeks were assessed by 3 reviewers. 36 were rewarded and scored higher than 0.

• @fego has reviewed 23 contributions with an average score of 52.78.
• @tobias-g has reviewed 13 contributions with an average score of 52.25.
• @crokkon has reviewed 1 contribution, with an average score of 45.

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

---

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