-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid class name exception on db-migration files #38
Comments
We use the following exclusions does this work for you?
|
No, it doesn't work. Even used your exclusion list in BuildConfig.groovy, but error is the same. |
Now I switched on Grails forked mode for test env (was set to false in grails.project.fork as you've written it is not supported in the coverage plugin for now), and it seems the exclusion works then, but after the unit test, I get:
|
This is how the test is performed:
when disabling forked mode, "Invalid class name" error for all migration files reoccurs. |
Environment:
code-coverage 2.0.3-3
Grails 2.4.4
Fork mode disabled in test
I use database-migration files of name
This leads to coverage errors on all of those files (see below).
I'm unable to exclude those files in the config to get rid of the error. Tried with
The text was updated successfully, but these errors were encountered: