udo: The unit test frameworks will track bugs not detect them. The detection part is done by the unit tests.
a unit test framework will help you write unit tests, no? that is one part of many things that a unit test framework can help you with. in fact, a unit test framework will help you detect bugs more than "track" them. a bug tracking system is complementary to a unit test framework (i.e. use junit for unit testing and as a unit testing framework, use bugzilla/jira to track bugs).
udo: In my opinion the detection part is the hard work. The tracking and reporting is trivial if you are a one person project. You just call all you unit tests and print the output. Unless you expect hundreds of tests to fail on a regular basis you do not desparately need a fancy framework.
tracking and reporting bugs is non-trivial. have you looked at frameworks and web applications dealing with bug tracking and/or reporting? you're arguing that these items/tools/practices are not relevant to a "one person project", and, in my opinion, that is wrong. i have taken on many contracting positions involving "one person" (just me) in software engineering, and i do use bug tracking software, unit testing framework, version control, etc...
udo: If you want to contribute a unit test framework feel free to do so.
i might need to given your helpful comments and code here.
udo: Just out of curiosity: what are those other industry standards you apply?
in regards to software engineering: unit testing, design patterns (mvc, ioc, fc, etc...) , agile development (xp), version control, continuous integration, etc...