Page tree
Skip to end of metadata
Go to start of metadata

The purpose of a defect report is to get an issue fixed as soon as possible so that you, as the client, will continue using the software

Please send a description of your issue with relevant images and files attached to:

Please include the one of the following in the Subject of your email:

  • Feature request: short description  - OR -
  • System issue: short description  - OR -
  • Issue: short description

Brief Explanation as to The Importance of a Defect Report:


Defect reports contain details of actions in the software application that don't get the expected result. Either the user receives an unexpected error, the system hangs, or expected calculations or data aren't accurate. Defect reports provide vital information for the development team to fix areas of the application that don't work properly.

The defect report is the most effective manner of communicating, tracking, and explaining defects. The more logical, organized, and detailed the report, the more likely that both QA and a developer can reproduce it without assistance or without having to request more information.

Defect reports need to include details about the component, version, environment, or other technical information to create a thorough description. Your defect report needs to be clear and easy to read. Remember that the purpose of a defect report is to get an issue fixed as soon as possible so that you, as the client, will continue using the software.

Guidelines for Submitting Defects to the GOBii Team:

Required Information in the body of your email or as an attachment:

  • Description
  • Component/Version
  • Steps to reproduce
  • Expected results
  • Actual results
  • Supporting Evidence

Description: Keep textual descriptions succinct and direct

Component/Version: either the LoaderUI or Extractor

Steps to reproduce: must be accurate. If you cannot reproduce the defect every time, include that in the report. Repeat the steps to reproduce several times, and verify you that have the correct steps and actions in the correct order that are necessary to reproduce the defect. Be specific as to which button, link, or action you used and how you used it.

Expected Results: Behavior you expected to see as a result of the steps you listed above

Actual Results: The behavior you are actually seeing as a result of the steps you listed above

Supporting evidence: attachments in the form of screenshots and/or videos as well as any logs, emails*, and error messages.

*It is very important that you attach/copy any emails that you receive from the LoaderUI or Extractor so that we can see all the information provided there.

Defect Report Template:

Sample Defect Report: <GSD-385>

Description: Marker Wizard & Dataset Wizard - Linkage Group and Marker Linkage Group mapping Error msg popup includes a NullPointerException rather than the correct msg

Component/Version: LoaderUI (Marker Wizard & Dataset Wizard) / rel 1.3

Steps to Reproduce:

  • select Marker Wizard
  • Select PI, project, Exp, Dataset, and Mapset
  • browse for file on local
  • double click file to upload
  • select file type as .txt
  • select <Preview Data>
  • select header position and coordinate -> Next
  • <Next>
  • map marker_name in left column of Data File Fields -> Linkage Group (name)
  • map linkage_group_name in left column of Data File Fields -> Marker-Linkage Group (linkage_group_name)
  • <Next>

Expected result:
error msg popup alerting me that Marker-Linkage Group (linkage_group_name) does not match Linkage_Group (name)

Actual Result:
Invalid Error msg pop-up stating "Error Validation when pressing Next: java:NullPointerException"

NOTE: The same behavior is in the Dataset Wizard for these same mappings

Supporting Evidence: see Screenshot attached <see GSD-385>

  • No labels