Skip to content

JUnit5 migration #358

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 10 commits into from
Apr 17, 2025
Merged

JUnit5 migration #358

merged 10 commits into from
Apr 17, 2025

Conversation

Fantoom
Copy link
Contributor

@Fantoom Fantoom commented Apr 13, 2025

Closes #353

Closes #291

@ForNeVeR ForNeVeR self-requested a review April 13, 2025 20:05
@ForNeVeR ForNeVeR self-assigned this Apr 13, 2025
@Fantoom Fantoom marked this pull request as ready for review April 14, 2025 15:54
Copy link
Collaborator

@ForNeVeR ForNeVeR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ForNeVeR
Copy link
Collaborator

Uhh, the macOS failure is suspiciously sticky. I suspect we have some issue about the remapped temp folder again. Will investigate tomorrow.

@ForNeVeR ForNeVeR merged commit 37d0597 into ant-druha:master Apr 17, 2025
6 checks passed
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.

Migrate tests to JUnit 5
2 participants