Draft:Software bug reports

Submission declined on 2 May 2024 by CanonNi (talk).

The proposed article does not have sufficient content to require an article of its own, but it could be merged into the existing article at Bug tracking system. Since anyone can edit Wikipedia, you are welcome to add that information yourself. Thank you.

If you would like to continue working on the submission, click on the "Edit" tab at the top of the window.
If you have not resolved the issues listed above, your draft will be declined again and potentially deleted.
If you need extra help, please ask us a question at the AfC Help Desk or get live help from experienced editors.
Please do not remove reviewer comments or this notice until the submission is accepted.

Where to get help

If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews.
If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed.

How to improve a draft

Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia.
Help:Wikitext – how to use the markup
Help:Referencing for beginners – how to include references
Wikipedia:Article development – how to develop your article
Wikipedia:Writing better articles – how to improve your article
Wikipedia:Verifiability – make sure your article includes reliable third-party sources

You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article.

Improving your odds of a speedy review

To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags.

Add tags to your draft

Editor resources

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL
Easy tools: Citation bot (help) | Advanced: Fix bare URLs

Declined by CanonNi 22 days ago. Last edited by CanonNi 22 days ago. Reviewer: Inform author.

Resubmit

Please note that if the issues are not fixed, the draft will be declined again.

Software bug reports are submitted to describe deviations from the defined behavior of a software program^[1]. They are also known as issue reports, trouble reports, or incident reports. This number can be very high in large-scale software development.

Each bug report contains several fields depending on the template a particular organization may be using. However, typically, they contain the following fields:

Bug Id: A unique identifier for a bug report.

Heading/Summary: A bug report may contain a heading/summary that briefly describes the bug.

Description: A detailed description is often mandatory for submitting a bug report, which may include steps to reproduce and patch.

Priority: The priority of the bug report, e.g., high, medium, or low.

In practice, bug reports are supposed to be submitted to describe an issue in the code. However, several bug reports are often submitted describing issues in documentation or requesting new features. Such issues are also known as invalid bug reports^[2]^[3]. Thus, early identification of bug reports describing code issues is important for companies.

References edit

^ Davies, Steven; Roper, Marc (2014-09-18). "What's in a bug report?". Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement. ESEM '14. New York, NY, USA: Association for Computing Machinery. pp. 1–10. doi:10.1145/2652524.2652541. ISBN 978-1-4503-2774-9.
^ Laiq, Muhammad; Ali, Nauman bin; Börstler, Jürgen; Engström, Emelie (December 2023). "A data-driven approach for understanding invalid bug reports: An industrial case study". Information and Software Technology. 164: 107305. doi:10.1016/j.infsof.2023.107305. ISSN 0950-5849.
^ Fan, Yuanrui; Xia, Xin; Lo, David; Hassan, Ahmed E. (2020-05-01). "Chaff from the Wheat: Characterizing and Determining Valid Bug Reports". IEEE Transactions on Software Engineering. 46 (5): 495–525. doi:10.1109/TSE.2018.2864217. ISSN 0098-5589.

[1] Davies, Steven; Roper, Marc (2014-09-18). "What's in a bug report?". Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement. ESEM '14. New York, NY, USA: Association for Computing Machinery. pp. 1–10. doi:10.1145/2652524.2652541. ISBN 978-1-4503-2774-9.

[2] Laiq, Muhammad; Ali, Nauman bin; Börstler, Jürgen; Engström, Emelie (December 2023). "A data-driven approach for understanding invalid bug reports: An industrial case study". Information and Software Technology. 164: 107305. doi:10.1016/j.infsof.2023.107305. ISSN 0950-5849.

[3] Fan, Yuanrui; Xia, Xin; Lo, David; Hassan, Ahmed E. (2020-05-01). "Chaff from the Wheat: Characterizing and Determining Valid Bug Reports". IEEE Transactions on Software Engineering. 46 (5): 495–525. doi:10.1109/TSE.2018.2864217. ISSN 0098-5589.

[1]

[2]

[3]