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

in #utopian-io3 years ago (edited)

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 55: January 10th - January 17th
  • 20 Contributions, 19 scored higher than 0
  • An average score of 50.39
  • 10 unique contributors
  • 1 Staff Pick

The contributions

ContributorURLProjectScore
@harry-heightzesteemapp-v2-android-version-doesnt-show-tables-created-in-markdown-after-post-is-publishedesteem V248
@blockchainstudiomissing-zlib-libraries-macos-steem-buildsteemit/steem90
@horpeyesteem mobile v2-using html image tag as the first line of a post crashes appeSteem V257.5
@horpeyesteem mobile v2 does not render center tag correctlyeSteem V248
@horpeyesteem mobile v2 does not render html image tag and direct image link correctly in preview tabeSteem V245
@blockchainstudiobusy-reblogged-by-not-shownbusy.org63
@anthonyadavisiitypeerror-on-getblog-via-beem---multiple-nodes-testedsteemit/steem45
@tobias-gknacksteem-loading-site-via-http-doesnt-redirect-to-httpsknacksteem.org80
@rufansesteem-mobile-v2-user-s-name-is-set-to-undefined-after-making-changes-via-settingseSteem V248
@horpeyesteem-mobile-v2-does-not-show-push-notification-iconeSteem V245
@difelice5000unusual-behavior-when-navigating-through-steemit-own-error-or-platformsteemit/steem12
@blockchainstudiobusy-new-reply-does-not-refreshbusy.org60
@face2facepost-time-syncing-issue-in-esteem-mobile-v2-0-6eSteem V232.5
@horpeyesteem-mobile-v2-push-notification-does-to-save-it-setting-on-exiteSteem38
@horpeyesteem-mobile-v2-using-capital-letter-tag-crashes-appeSteem V241
@syedumairreblog-option-is-not-hidden-for-author-s-own-post-on-esteem-mobile-v2-2-0-6eSteem V260
@horpeyesteem mobile v2-responding to a reply crashes appeSteem V270
@valchizvideo-option-not-working-showing-camera-insteadeSteem V20
@blockchainstudiotag-not-working-when-clickedeSteem V236.5
@face2facecurrency-setting-is-not-working-properlyeSteem V238

This week we had 20 contributions, more than we've had in the previous 3 weeks. Majority of the reports were submitted to the project repository of eSteem mobile V2.

19 out of the 20 reports were scored higher than 0.

Also, we had a staff pick from @blockchainstudio, that's 2 picks in 2 weeks for the super bug detector :) This time he found that building steem on Mac OS does not work, instead it returned the error - Could NOT find zlib (missing: ZLIB_LIBRARIES).

Cause

Most MacOS version has dynamic library of zlib by default, as you can see from /usr/lib/libz.dylib (you can't even write in /usr/lib unless disabling SIP, which is not recommended), but no static library. But the build script keeps trying to find static library, libz.a in the same directory, even if you give export ZLIB_LIBRARIES=$(brew --prefix)/Cellar/zlib/1.2.11/lib/ correctly.

He made a pull request that rectified this error. You can read the full report here - https://steemit.com/utopian-io/@blockchainstudio/missing-zlib-libraries-macos-steem-build.

Apart from the staff pick, there were also notable contributions from @tobias-g and @horpey. Tobias observed that the site https://knacksteem.org is not usable via http://. The site does not automatically redirect a user, it will instead cause cross-origin errors and the categories will not be loaded.

Horpey made 7 contributions to the eSteem application. In total, the project received 14 bug reports.

Weekly Average Score and number of Contributions

image.png

image.png

Chart breakdown:
  • The average score this week is 50.39.
  • The average score is approximately 5% lower than the 2 week average of 53.04.
  • This week's average is lower than the last 2 weeks average by 0.61.
  • It is lower than last week's average of 61.42 by 11.03.
  • 7 contributions were scored higher than the week's average.

Hunter Totals and Average


image.png


image.png

Chart breakdown:
  • This week we had 10 unique contributors.
  • There were 11 reports from the top contributors. 7 contributions from @horpey and 4 from @blockchainstudio
  • As it stands, @horpey is the category's top contributor with 9 finds. That is 9 finds since the start of the new year, he's closely followed by @blockchainstudio with 7.

Reports Reviewed By Reviewer

image.png

image.png

Chart breakdown:

The category has received 26 contributions since the start of the year. The contributions received by the category in the past 2 weeks were assessed by 3 reviewers. 25 were rewarded and scored higher than 0.

  • @fego has reviewed 17 contributions with an average score of 54.15.
  • @tobias-g has reviewed 8 contributions with an average score of 51.5.
  • @crokkon has reviewed 1 contribution, with an average score of 45.

Common Mistakes And How To Fix Them

Following the suggestions made by @tykee, I thought I'd borrow a leaf from the works of @favcau and @didic :). So in this section, I will be highlighting the common mistakes found this week, and I will be offering tips on how to avoid them in future contributions.

1. Contributions with scores below 25

Both the title and content of the submission post were lacking in information and the steps to bug reproduction were badly explained and, at times, impossible to follow.

  • The post title ought to include the app name and version number, as well as a brief description of the occurring issue. In other words, the title should be well detailed enough to provide an insight as to what the bug is about.

  • The steps should be clear and easy to follow. It is advised to have the steps arranged in an ordered list, that way it is easier for the PO to follow and reproduce the error step by step. Also, the video should only add value to the report and not totally replace the written steps or essential details of the bug.

2. Contributions scored 0

This particular feature has not been implemented yet, and because of this, this particular issue cannot be considered a bug within the application

A bug is a manifestation of an error in the functionality of a system and is a deviation from the expected behavior, usually traced back to a coding mistake. An unimplemented feature, on the other hand, has no expected behavior or user story. This is simply because the function is not defined, hence there is no clear idea of how the feature should behave.

  • One way to avoid mistaking an unimplemented feature for a bug is to wait for the PO to acknowledge the issue as a bug since he's responsible for defining the functionalities.
  • Another option is to go through the github repo to confirm that there is a code implementation of the expected behavior. If there is no code to support the particular action then it is yet to be implemented and is not a bug.

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

Sort:  

What a pleasant week in the Bug-hunting category. It's great that the category received cool submissions like these. @blockchainstudio continues to rule the Bug category as the MVP. Honor to him!
This report is informative, and all data are well described. Your tips are good, but you could make your texts more friendly. I.e. " were badly explained'' not explained in great details sounds friendlier. Nonetheless, those tips are cool and should be useful for hunters.

Thanks and have a great week!

Please note that while the CM hasn't changed the footer, I am not scoring #iamutopian posts based on the questionnaire. They have their own metric, and that will be the case until we go live with the new guidelines and new questionnaire, which will be comprehensive enough to reflect these types of posts.

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? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]

Hi @tykee, thank you for mentioning me :)

I hope to mention you more in coming weeks:))

곰돌이가 @blockchainstudio님의 소중한 댓글에 $0.005을 보팅해서 $0.018을 살려드리고 가요. 곰돌이가 지금까지 총 2725번 $33.507을 보팅해서 $33.851을 구했습니다. @gomdory 곰도뤼~

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

Hi @tykee

This statement - "Both the title and content of the submission post were lacking in information and the steps to bug reproduction were badly explained and, at times, impossible to follow" is exactly the same as it is in the questionnaire. It is one of the answers to the question - How would you rate the descriptiveness and clarity of the submission post?

So it's not like I directly used it in reviewing or describing a post or a particular contributor. The aim of the tip was to show the hunters how to avoid being scored with this option in the questionnaire.

Thanks for the review though. I will try and be more specific in the weekly overviews to follow.

Congratulations! Your post has been selected as a daily Steemit truffle! It is listed on rank 10 of all contributions awarded today. You can find the TOP DAILY TRUFFLE PICKS HERE.

I upvoted your contribution because to my mind your post is at least 11 SBD worth and should receive 252 votes. It's now up to the lovely Steemit community to make this come true.

I am TrufflePig, an Artificial Intelligence Bot that helps minnows and content curators using Machine Learning. If you are curious how I select content, you can find an explanation here!

Have a nice day and sincerely yours,
trufflepig
TrufflePig

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

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!

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

You got more than 400 replies. Your next target is to reach 500 replies.

Click here to view your Board
If you no longer want to receive notifications, reply to this comment with the word STOP

Support SteemitBoard's project! Vote for its witness and get one more award!