I've been dealing with bugs in a very ad hoc fashion, mostly hitting them as they come or trying to write a note in my code to deal with them.
As my codebase has broken the 50000 loc mark I find it's harder and harder to remember all my little issues and ideas, so I want to add a testing framework and bug tracker to my application dev suite. Problem is I'm unsure the best way to track bugs in an application (the testing will obviously just hook into
"MUnit`", following Jason B's usage pattern).
It's relevant to note that I do all of my work entirely within the FE (thanks to Kuba for pointing out that this is worth mentioning). Because of this unless you think I am being entirely unreasonable (let me know if you do), I would really prefer not to have to open another program to log these bugs or TODO notes.
What is an effective way to tackle this problem?
My only thing is that I would strongly prefer to have it in pure Mathematica so that I can easily link the framework into my existing code base.
Can anyone convince me of the sheer ridiculousness of this or suggest a minimal prototype for a simple, extensible, programmable version of this?