Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CI failing due to use of another test driver #354

Open
martinezmatias opened this issue May 4, 2022 · 1 comment
Open

CI failing due to use of another test driver #354

martinezmatias opened this issue May 4, 2022 · 1 comment

Comments

@martinezmatias
Copy link
Collaborator

The CI is failing because maven uses TestNG instead of jUnit (log here). Consequently, instead of calling one test per job it calls all tests from the test cases which produces a timeout.
martinezmatias added a commit that referenced this issue May 4, 2022
@martinezmatias
forcing Specifying a Provider issue #354
8970171
@martinezmatias
Copy link
Collaborator Author

Problem identified: the sure-fire detected the TestNG dependency (Gzoltar depends on it) and use its engine. As solution, we force to use a particular test engine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@martinezmatias