From the course: Software Testing Foundations: Bug Writing and Management

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Traditional bug forms and responses

Traditional bug forms and responses - Jira Tutorial

From the course: Software Testing Foundations: Bug Writing and Management

Start my 1-month free trial

Traditional bug forms and responses

“

- [Instructor] While there are a variety of bug tracking tools, and most of them may be configured and customized for your project, there are some core fields that most bugs submission forms have. Sometimes they may be named differently and different tools like Centercode or JIRA may handle them in a different way. At their core they are there to help you clarify and deliver the issues you discover. The first field you'll see often is the summary. It's a brief overview of the book. It's a concise and clear representation written in case style, or sentences uniformly used across all the bugs. This field usually adheres to a specific set of vocabulary so that people reading the bug know what it's exactly about without having to review its contents. The description is self-explanatory. This field can be broken into two different sections where one details the steps to duplicate and the other contains relevant information…

Contents