Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@brendensoares
Copy link
Member

Need to consider the side effects. At the very least, this allows me to run my module's tests along side the main app's tests.

Also, we should refactor the "hack"; is there a better way to enables testing in an app other than a hard coded module check like this?

Is there a better way to enable tests per module?

@notzippy
Copy link
Collaborator

Recommend passing in a flag from the revel/cmd to indicate the core app that revel is to add in all folders for modules that contain tests. Additional feature could be to filter tests by module

@brendensoares
Copy link
Member Author

@notzippy I kind of prefer doing that via app.conf if at all. I think our goal should to use convention over configuration.

It makes sense that if the module has a tests folder that we make use of it. Are there scenarios where that would backfire or be negative?

@notzippy
Copy link
Collaborator

I was just thinking there is no need to include those folders if revel was not running any tests - so harness would pass in something indicating what mode it should be run in..

@notzippy notzippy added status-tested Ready for release type-enhancement New enhancement of existing feature labels May 18, 2017
@notzippy notzippy added this to the v0.16 milestone May 18, 2017
@brendensoares brendensoares merged commit c64b8e1 into develop May 19, 2017
@brendensoares brendensoares deleted the feature/load-module-tests branch May 19, 2017 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status-tested Ready for release type-enhancement New enhancement of existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants