| [Bug?] | bug-triage |
Use this category if you think you have found a bug in the utPLSQL framework and want to discuss it before a formal issue is opened.
Once a maintainer confirms the bug, they will open an issue and link it back here. You do not need to open an issue yourself.
If you are certain it is a bug and can provide a reliable reproduction, you may open an issue directly instead.
Describe the unexpected behaviour. Include any error messages or stack traces.
Describe what you expected to happen instead.
Paste the minimal PL/SQL needed to reproduce the problem. The simpler, the better.
Any findings from your own debugging that might help narrow this down.