FAQ	bugpub[AT]bugpub.com

Social Bug Tracking and General Topics

How to fill out new Bug form in right way?
Why I cannot delete Bug or status Update/Comment?
How I can delete Bug or status Update/Comment?
How I can update Bug or status Update/Comment?
What is Defect Cost?
How Defect Cost can be calculated?
What is Bug Workflow on BugPub.com?
What User roles may exist on BugPub.com?
Who will fix found bugs?
When and how Bug contests will be announced?
What are conditions to get recommendations on LinkedIN?
Are there supposed any other kinds of rewards?
Besides of that, What are benefits in participation on BugPub.Com for me?
Which authorization systems are supported?

Learning Testing

Coming soon...

Social Bug Tracking and General Topics

How to fill out new Bug form in right way?

Generic rule is providing as much relevant information as possible while get rid of redundancy. Each field should be carefully filled in since quality of bug report eventually defines how quickly and certainly it will be identified and then fixed.

Defect Summary should uniquely and briefly provide context and outcome of the found bug. Here are few examples:

“System is crashing with thrown exception #923 upon uploading 3rd party feed” “There is security vulnerability in module responsible for session handling” “Double click on Table grid causes unexpected page reload”

Bug report details basically describe preconditions of test, certain steps to reproduce, actual and expected results. In addition, details can provide some specific information for reproduction and stability of the reproduction, impact for user, suggestion on how to fix or enhance

We appeal to select values in Severity, Outcome and Test Type deliberately. These fields are very important in defect localization and further identification.

Additional fields plays vital role in defect identification and localization, especially fields concerning User’s environment: browsers, languages, Oss, etc. It is highly recommended to provide as more details as possible because ultimately all information contribute to defect cost

Important Notice: please report and update Bugs carefully and deliberately. BugPub does not provide neither prepublishing sandbox nor functionality to storing bugs privately, also please read Why BugPub does not have direct capability to remove and edit your records

Why I cannot delete Bug or status Update/Comment?

Software Industry standards does not welcome Issue (bug) deletion as well as comments and status updates. The following reasons are behind that:
- Other stakeholders may not get notified upon changes and eventually causes mess ups
- History should be kept for audit trailing
- This approach brings up to report high-quality bug reports and updates from first time.
Instead of direct update, User can provide some updates within comments. Another approach implies bug history change tracking that available for all viewers. BugPub does not have functionality to update records directly as well as keeping change history. For available options on update or delete records, please see next 2 Questions-Answers below.

How I can delete Bug or status Update/Comment?

To delete a bug, you can mark it Deleted in status updates, while community has a right to restore or request update from owner. If community is not requesting update or does not restore your issue within 48 hours – the issue will be deleted and no longer available for view on BugPub.

It is impossible to delete status update and comment. BugPub keeps history of what people are responding. Providing capability to delete status update can break an issue history chain due to tough dependencies (consider case when your comment and/or status update is in the middle of the thread)

How I can update Bug or status Update/Comment?

To update a bug, you should provide additional details within Comment box.

If you believe your previous comment is wrong, you can submit new comment that will notice to others to consider that comment as wrong one.

What is Defect Cost?

We define the defect cost by the following core properties:
- Priority for business
- Severity and Impact for Users community
- Quality of provided information about found bug
- Complexity in reproduction
- Precision of provided information
- And timeliness of providing feedback (upon clarification process, e.g. when developer requests more information)

How Defect Cost can be calculated?

We weigh relative Bug Cost as follows:


Bug Cost = (Priority) * (Severity) + (Quality) *(Complexity) + (Precision) + (Timeliness)

Each of given parameter can be only integer in range of 1-4

Examples:
Bug Cost = 2*3 + 1*3+2+4 = 15
Another Bug Cost = 4*4 + 1*2+1+1 = 20

What is Bug Workflow on BugPub.com?

We will keep it pretty straightforward like shown on diagram below. Please update bugs carefully and honestly:

What User roles may exist on BugPub.com?

For now we have 3 types of user in context of a particular bug:

Reporter – logged in with LinkedIn profile which submitted the bug. This role has appropriate available Statuses

Contributor – logged in with LinkedIn profile which can update status and/or comment on bug. This role has appropriate available Statuses

Viewer – anyone in Internet (no matter logged in or not) may view the bug and share the link

Who will fix found bugs?

We will work hard to promote discovered issues to backlogs of end Projects. As we are resource of bugs, we will appeal to producer in order to keep tracking for BugPub.Com repository and react proactively.

When and how Bug contests will be announced?

We will have dedicated page for that as well as random banners will be displayed on viewing pages

What are conditions to get recommendations on LinkedIN?

There are 2 ways to get recommendation(s):

1) From Company that appreciate found defects by User

2) From BugPup.com for high quality found defects. We don’t have specific thresholds it is individual. E.g. you may find just one critical flaw in operating system and by this get even 2 recommendations – from us and from Company

Are there supposed any other kinds of rewards?

We are continuously working on that. Other types of rewards are not limited by 3rd parties – Companies and Projects are free to encourage community and individuals in any way they wish. In this business, BugPub.com poses as communication mediator. BugPub.Com is not accountable for relationships between Users and Companies in the matter of motivation and encouragement.

Besides of that, What are benefits in participation on BugPub.Com for me?

BugPub.com is open community for everyone and of any skills set in testing. The value of improving quality of software is invaluable. Moreover BugPub.com is a tool for wetting feet in testing, improving testing skills, expansion of personal profile and professional network.

Which authorization systems are supported?

Only LinkedIN network. The reason behind that is necessity to build professional network and explicitly to be repository of high quality bugs from real people.

Read Our Terms and Conditions & Privacy Policy