Archive - TestRail RSS Feed

Bug Report Example

Reporting bugs found during the software development lifecycle in a clear and concise way is critical to fast, in-cycle resolution.  The scrum team I work on uses the Jira bug tracking tool which integrates very well with our test case software, TestRail.  It is extremely helpful to developers when QA Engineers provide consistent and relevant information to assist the developer in locating and addressing the specific issue.  Here are some sample details we require QA to provide in every bug report:

Bug Name: 500 Server Error When Adding a Comment > 2000 Characters
Bug #: (Automatically added by Jira or other Bug tracking tool)
Type: Bug
Status: To Do
Priority:  High/Medium/Low
Affects Version/s: Version Number
Component/s: Software components
Environment: QA
Sprint: Sprint ##.##
Assigned to: Developer Name
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Dev/QA/Staging/Production

Description:
Application crash on clicking the Add Comment button when a comment has more than 2000 characters.

Steps To Reproduce:

  • Log in to Application
  • Navigate to Attendance Page
  • Enter attendance
  • Select Date
  • Enter text > 2000 characters
  • Click Save Comment

Expected Result:
Should receive error stating cannot exceed 2000 characters

Actual Result:
Receive a 500 Internal Server error

Stack Trace:
If you have access to database logs or similar, include as much of the exception details as possible.  This may involve filtering through a lot of records to locate the exact stack trace for the exception.  This can save developers a significant amount of time which is win win for the whole team.