Regression testing policy

All problem/bug reports should include a reproduction recipe in form of a script/program which starts out with an empty state and runs a series of commands/functions/methods to trigger the problem, be it a crash or some other undesirable behavior.

Please take this request very seriously; Ask for help with writing your regression test before asking for your problem to be fixed. Time invested in writing a regression test saves time wasted on back-and-forth discussion about how the problem can be reproduced. A regression test will need to be written in any case to verify a fix and prevent the problem from resurfacing.

If writing an automated test really turns out to be impossible, please explain in very clear terms how the problem can be reproduced.