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

Migrate all tests to JUnit 5 #3959

Closed
stefan-kolb opened this issue Apr 16, 2018 · 9 comments
Closed

Migrate all tests to JUnit 5 #3959

stefan-kolb opened this issue Apr 16, 2018 · 9 comments
Labels
good first issue An issue intended for project-newcomers. Varies in difficulty. type: code-quality Issues related to code or architecture decisions

Comments

@stefan-kolb
Copy link
Member

stefan-kolb commented Apr 16, 2018

  1. Migrate all remaining tests
  2. Remove obsolete Gradle dependencies & configurations
@stefan-kolb stefan-kolb added the type: code-quality Issues related to code or architecture decisions label Apr 16, 2018
@Siedlerchr
Copy link
Member

Our Importer/Exporter and a lot of our other tests rely on this feature:

Refs junit-team/junit5#1247
Currently planned for RC1

@LinusDietz
Copy link
Member

Do we really need to migrate? The Junit5 vintage engine should run the old junit4 tests. I already removed the old dependencies at #3580

@stefan-kolb
Copy link
Member Author

@LinusDietz Good question. If JUnit 4 support does not introduce additional dependencies, but is included in JUnit 5 per default, it is really just nice to have migration and not necessary. Could also be a nice beginners task then.

@tobiasdiez
Copy link
Member

It is a separate dependency

testRuntime 'org.junit.vintage:junit-vintage-engine:5.2.0-M1'

It would be nice to migrate all tests at some point to JUnit 5 but there is no real urgency in doing this. For now the only blocker is the temporary file / folder extension (although we could just copy the one provided in the junit sample rep), which, however, only affects a very small subset of our tests.

@tobiasdiez tobiasdiez added the good first issue An issue intended for project-newcomers. Varies in difficulty. label Apr 18, 2018
@Siedlerchr
Copy link
Member

The TempoaryFolder extension will be published in the junit-pioneer project: junit-pioneer/junit-pioneer#39

@tobiasdiez
Copy link
Member

The TempDir extension is now part of https://github.com/junit-pioneer/junit-pioneer and a test conversion to this extension can be found in 3c6bbd2 (sorry for pushing it directly onto the master).

@Siedlerchr
Copy link
Member

Very good. So then we can go ahead converting the rest. I think this was the only issue left.

@tobiasdiez
Copy link
Member

Thanks to @Metatronwings most of the tests are now converted. A few things remanin to be done (see #4260 (comment)), but require a new version of ArchUnit and/or JUnit. Thus, I put this issue on-hold for the momen.

@koppor
Copy link
Member

koppor commented Oct 9, 2019

Adressed by #5394.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue An issue intended for project-newcomers. Varies in difficulty. type: code-quality Issues related to code or architecture decisions
Projects
None yet
Development

No branches or pull requests

5 participants