Reporting Bugs In Database: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 1: | Line 1: | ||
This document describes how you need to register a issue in the database. | |||
=Found by= | =Found by= | ||
At found by you fill in the person who has reported the issue, for customers select the company name. | At found by you fill in the person who has reported the issue, for customers select the company name. | ||
Revision as of 12:36, 23 January 2007
This document describes how you need to register a issue in the database.
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.
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