JUCE testing

What kind of testing do you do? Are there some commits that are more fully tested than others?

There’s no simple answer to that, because the library’s content is so varied, and the types of commits vary from trivial stuff to huge new features. There are some unit tests for lower level classes, but that’s not really possible for GUI or audio stuff, so I just test those things in whatever way is appropriate for whatever I’m working on.

Speaking of this… I noticed that the MD5 algorithm has no UnitTest. I think it could be a good idea to add some there, to check that nothing breaks between builds (I may be wrong, but I seem to remember that SHA1 has proper testing instead)

Thanks, good point - will do…