Rubberduck: Bug: Unit Testing - Multiple test modules

Created on 27 Mar 2018  路  2Comments  路  Source: rubberduck-vba/Rubberduck

Unit testing work perfectly if I have only 1 testing module, but the moment i added a second testing module the @ModuleInitialize stopped running, and that means that Assert and Fakes don't get initialized, and so I can't run the tests.

I am testing 2 different classes, so it would be ideal to have 2 different test classes.

I moved the code to the same test class and everything went ok.

I'm on version 2.1.1.2532 and Access 2013.

Cheers

bug duplicate

Most helpful comment

This was a known issue and was fixed in the PR #3778, which is a pre-release, v2.1.2.3005. So if you want to run a pre-release, you can get the current pre-release and try it again.

All 2 comments

This was a known issue and was fixed in the PR #3778, which is a pre-release, v2.1.2.3005. So if you want to run a pre-release, you can get the current pre-release and try it again.

I'll wait for the release.

Thanks and keep up the amazing work!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

zspitz picture zspitz  路  28Comments

bclothier picture bclothier  路  33Comments

brab picture brab  路  49Comments

ThunderFrame picture ThunderFrame  路  23Comments

AndrewM- picture AndrewM-  路  37Comments