OneTrueError - A tool to find quality issues in released software.

OneTrueError delivers facts regarding how many errors your application have, how often they occur and the number of affected users. All done within seconds from when the error was detected without relying on any third party.

Problem statement

Error/bug management is typically initiated by an error report from an user to a support department. The report is analyzed by the support department and is either categorized as an bug or as an user error. Bugs are sent to the development team, user errors are discarded.

Typical issues with this approach

  • Users do not report bugs
  • Real bugs are mistaken for user errors by the support department
  • User errors are interpreted as bugs by the support department
  • Logged errors are missed due to large log files
  • Logged errors are missed due to logs not being reviewed continuously.
  • Duplicate bug reports are treated as new.
  • Log files are inaccessible on client computers

Those issues significantly increases the amount of administration required before bugs can be reproduced and corrected.

The OneTrueError approach

OneTrueError automates the entire error management process by detecting and analyzing errors in real time. OneTrueError makes the bug correction process more cost efficient by including information that typically is forgotten in manual bug reports and by eliminating the need to administer the issues mentioned above.

OneTrueError can answer the following questions seconds after an error has been automatically detected

  • What information did the user enter to generate the bug?
  • How often is the error occurring?
  • How many users have the problem?
  • Which application version has the problem?
  • What information is required to reproduce the error?
  • Which users want to be contacted with status updates?
  • How did the user describe the error?


The entire process is now based on facts without loosing information on the way from the application to the development team. All reports that the development team receives are proven to be actual errors and typically include all information required to correct the issue.