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

Migrate to jUnit 5 #628

Closed
opatrascoiu opened this issue Jan 25, 2024 · 1 comment
Closed

Migrate to jUnit 5 #628

opatrascoiu opened this issue Jan 25, 2024 · 1 comment
Assignees
@opatrascoiu
Labels
enhancement New feature or request

Comments

@opatrascoiu
Copy link
Collaborator

Expected Behavior

Actual Behavior

jDMN Version where this issue was observed

Steps to reproduce the behavior
@opatrascoiu opatrascoiu added the enhancement New feature or request label Jan 25, 2024
@opatrascoiu opatrascoiu self-assigned this Jan 25, 2024
@Fiend-Star
Copy link

Fiend-Star commented Feb 19, 2024 •
edited
Loading

Hi @opatrascoiu , While migrating to Junit 5, how would Fitnesse dependencies be handled? As they are not compatible with junit 5 and we may have to use junit vintage for junit 5 backward compatibility for fitnesse.

opatrascoiu added a commit to opatrascoiu/jdmn that referenced this issue Feb 22, 2024
@opatrascoiu
[goldmansachs#628] Migrate to jUnit 5. Add missing dependency to vintage
3c40933
opatrascoiu added a commit that referenced this issue Feb 22, 2024
@opatrascoiu
Merge pull request #646 from opatrascoiu/junit5
d625eab 
[#628] Migrate to jUnit 5. Add missing dependency to vintage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@opatrascoiu opatrascoiu

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@opatrascoiu @Fiend-Star