How to provide bug reproduction scenario to Invantive

This topic describes the steps to provide a good reproduction scenario on a bug to Invantive.

Bug Reproduction Scenario

Upon reporting a bug about Invantive products, Invantive support expects you to provide a reproduction scenario. Our development team can not reliably fix problems without a reproduction scenario. Also, the costs of poking around a presumed bug is extensive. Bug reports missing a complete reproduction scenario can not be honored. In cases where a bug reproduction scenario can not be established it is possible to contact a dealer or consultant to get assistance in creating such a reproduction scenario.

A reproduction scenario must enable a person without access to your environment to reproduce the problem on a freshly installed PC with the latest production release of the Invantive product you are reporting a bug on. A reproduction scenario should be self-contained and complete.

Reproduction scenarios should be as simple as possible, with all steps found unnecessary removed in advance. It can take time to create a quality reproduction scenario from a business environment. Simplification also should ensure not to include private or sensitive information such as business numbers or passwords.

More information on adding relevant data to your bug report is described in the topic “Upload Data for Reproduction Scenarios”.

A reproduction scenario can contain some picture as a guidance, but an accurate textual description is foremost.

Example

Examples of good reproduction scenario are:

Setup steps

  • Create a database with the following data containers.
  • Log on to the database on product X.
  • Paste the following SQL statements into the query window.
  • Press F5.

Expected outcome

The expected result is that no error occurs. (Or that the process finishes within time Z or returns value A)

Actual outcome

The actual result is an error Y, which is incorrect since…

Verification

Upon receipt of your reproduction scenario the support engineer will execute your steps accurately. When the different behaviour between actual and expected outcome has been established, the expected outcome described will be matched against the expectations of the product owner.

When both support engineer and product owner agree the steps to describe a bug, an internal bug ticket will be created and associated with your bug report. This internal bug ticket will be handled by development.