Reporting Bugs In Database

This document describes how you need to register a issue in the database.

Items that need to be filled in are:

• Summary
• Type
• Component

Summary

When filling in the summary, be as detailed as you can without using the "found by" persons name. It could be that several people are reporting the same item.

Example:
Signal generator is giving problems during detection, EABO error.
Wrong: Signal generator is giving problems during detection, EABO error.
Right: the Signal generator(marconi 2024) is giving problems during detection, EABO error.

Found by

At found by you fill in the person who has reported the issue, for customers select the company name. For resellers can be specified at a person level.

Type

At type you define the type of report you are giving. is it a crash or a wish? see Explanation of the measurements type for the full explanation. With the type

Component

With component you can specify where the report is related to. for example, the signal generator problem is a device driver item.

• How do you determine the correct component?

By asking yourself some basic questions it should be very easy to find the correct component.

1. To which test is it related?
2. Is it driver related?
3. Is it during report generation?
4. During general configuration?

Explanation of the measurements type

• Incorrect measurement, no crash but the result information is wrong. Due to wrongly applying corrections or other calculations

Definition crash: the program is terminated incorrect, and you may get a report from Windows

• Crash data loss, RadiMation is crashing during a measurement.
• Crash data loss, RadiMation is crashing when not doing a measurement.
• unexpected functionality, everything that is going wrong except crashes and incorrect measurements
• Cosmetic, everything that has to do with the way it looks
• Wish, items that are wishes and need to be remembered for possible later implementation