-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add Surefire plugin #110
Add Surefire plugin #110
Conversation
Signed-off-by: see-quick <maros.orsak159@gmail.com>
Signed-off-by: see-quick <maros.orsak159@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, in all other projects we run the unit and integration tests with one step. Not sure if there is any reason to do it separately. If there is some reason for it and you want to keep it separate, its fine with me.
Hmmm, I wanted to do it simultaneously but now that I have mutation testing included I want to first check:
|
Ok. As I said, if it has some reason, it is fine with with me. |
Signed-off-by: see-quick <maros.orsak159@gmail.com>
Signed-off-by: see-quick <maros.orsak159@gmail.com>
This PR adds a surefire plugin to run UTs within the test container.