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.

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

Consider moving to TestNG? #4

Closed
chrisengelsma opened this issue May 16, 2017 · 1 comment
Closed

Consider moving to TestNG? #4

chrisengelsma opened this issue May 16, 2017 · 1 comment

Comments

@chrisengelsma
Copy link
Member

Currently, we're using JUnit 4 as a our test package. It's great for simple testing, but TestNG allows for much more granularity for individual test settings, as well as native support for concurrent testing.

The structure and annotations for both are close enough that migrating would be relatively trivial I think and require a small bit of refactoring.

@chrisengelsma
Copy link
Member Author

I've gone ahead and done the migration in my local fork, everything still works and now it zips along much faster now as it's testing in parallel on 5 threads. I will submit a PR unless anyone has a bleeding heart reason not to migrate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Test Coverage
Awaiting triage
Development

No branches or pull requests

4 participants