Skip to content

Consistent usage of TestNG #4885

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

Merged
merged 3 commits into from
May 7, 2025
Merged

Consistent usage of TestNG #4885

merged 3 commits into from
May 7, 2025

Conversation

frantuma
Copy link
Member

@frantuma frantuma commented May 7, 2025

Includes and replaces #4879 (fixes gradle test), @strangelookingnerd thanks!

This PR aims to remove usage of JUnit and consistently use TestNG across the modules instead.

Changes include:

  • Use TestNG annotations over JUnit counterparts
  • Use TestNG assertions over JUnit counterparts (also simplify some assertions in the process)
  • Consistently use static imports for TestNG assertions
  • Remove JUnit depencency if not required
  • Add TestNG dependency if required

There is one exception in swagger-maven-plugin where JUnit is still required by the underlying maven test suite and thus tests can not be migrated.

@frantuma frantuma merged commit 5b6a0f9 into master May 7, 2025
6 checks passed
@frantuma frantuma deleted the use_testng branch May 7, 2025 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants