Skip to content

Use junit5 instead of testng#172

Merged
aastha25 merged 2 commits into
linkedin:1.0.1-hotfixfrom
ramurm2013-droid:hotifx_junit
Oct 27, 2025
Merged

Use junit5 instead of testng#172
aastha25 merged 2 commits into
linkedin:1.0.1-hotfixfrom
ramurm2013-droid:hotifx_junit

Conversation

@ramurm2013-droid

Copy link
Copy Markdown
Contributor

No description provided.

@aastha25

Copy link
Copy Markdown
Collaborator

Build failed, PTAL.
And generally it's good to use a consistent testing framework across the project. If it's only a matter of replacing the imports, could you please apply the same changes to other modules?

@ramurm2013-droid

Copy link
Copy Markdown
Contributor Author

Build failed, PTAL. And generally it's good to use a consistent testing framework across the project. If it's only a matter of replacing the imports, could you please apply the same changes to other modules?

Fixed failures. Build is succeeding now.

@aastha25 aastha25 merged commit aca71b0 into linkedin:1.0.1-hotfix Oct 27, 2025
1 check passed
ramurm2013-droid added a commit to ramurm2013-droid/transport that referenced this pull request Jun 17, 2026
* Use junit5 instead of testng

* Fix failing tests

---------

Co-authored-by: Ramanathan Ramu <rramu@linkedin.biz>
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