The most important information in any defect, bug or exception documentation are the exact steps to reproduce a defect.

Without a clear understanding of the problem, any bug here may be incorrectly prioritized or incorrectly tracked.
Or the problem may be misunderstood and not immediately worked on a fix when the development team could have spent the time on a more serious issue.

Therefore, here are a few points to keep in mind:

The first thing the Support or Developer Team will do, when trying to find or fix a bug is, to try to reproduce it in the development environment. 
If the steps to recover the problem are not accurate or the steps do not result in the error occurring every time, the developer may assume that the problem has already been fixed as a side effect of another problem in the current environment.

Subsequently, he will return this error to the support team as non-reproducible. 
These types of delays can really hold up any case progress.


Before sending a bug report, please practice some due diligence.
Test the bug in standard Codesys environments using standard WinV3 control - if possible.

Also, any additional information that can be included may prove critical.

If a bug is attempted to be reproduced on a different system and in a different environment, there is a good chance that this will not be able to reproduce and will therefore ask for additional information.

If these things are documented and attached to the request in advance, this will save time and inquiries from the Support Team.


By recording the exact steps, that lead to the error, anyone investigating the error can correctly reproduce the steps and understand exactly what is being reported.

Not only does the Support Team need to correctly assign and categorize these bugs, but they also need to prioritize them for development in order to assign the correct severity to bugs and problems.


It is important that the bug is properly assigned to the required development team.
A single screenshot of a bug usually does not contain enough information to assign the problem to the correct team or problem group.

However, providing written steps leading to the screenshot of the bug, or a video of the steps, makes it easier to assign the correct resources to the problem.


Conclusion

Please take a little extra time when reporting issues to verify that you have taken the proper steps to reproduce an issue can prevent a bug from being passed from one team to another. 
Not only does this delay troubleshooting, but it can also lead to frustration for those trying to track down the problem. 

Keeping an accurate record of the steps leading to a bug is therefore an important general contribution for us, and ultimately for all customers, in order to lead to a faster bug fix, a possible workaround, or possible solutions.


If you need technical support, please purchase a Support Ticket in the CODESYS Store.
Note that certain products in the CODESYS Store already include a Support Ticket.

To report software bugs or if you have a question concerning the products in the CODESYS Store,
click on the "My Question" button next to the shopping cart in the CODESYS Store.



  • No labels