> > This is one of the "accepted practices" in writing tests from all the research that I've made. [Rightly or wrongly]
That would be correct, but with VBA not having a "solution" level that "contains" multiple projects, it's much simpler to keep the tests in the same project; since there's never been a first-party unit testing framework for VBA, VBA-specific guidance is pretty much inexistent. If you browse through Rubberduck's source code, you see that indeed we do have all the tests in the