Hi @Bananeweizen, we have windows builds as part of our CI and it works ok AFAIK.

I had a look at assertj-core/src/test/java/org/assertj/core/internal/paths/Paths_assertEndsWith_Test.java resutls and they pass:

2023-09-16T08:15:24.2101295Z [INFO] Running Paths assertEndsWith
2023-09-16T08:15:24.2246093Z [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 s -- in Paths assertEndsWith

Same for assertj-core/src/test/java/org/assertj/scripts/Convert_Junit_Assertions_To_Assertj_Test.java

2023-09-16T08:14:35.8067296Z [INFO] Running Convert JUnit assertions to AssertJ
2023-09-16T08:15:20.2271981Z [INFO] Tests run: 44, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 44.50 s -- in Convert JUnit assertions to AssertJ

So maybe it's something that is dependent on your machine (admin rights or something alike) ?

But that would mean that you are probably running your CI tests in a non standard way, with admin rights or special settings for the virtual machine. Contributors with a normal setup (and not running as administrative user all the time locally) should see the same issue as me.

The files we manipulate should all be under a temporary directory created by JUnit, which in turn delegates to Files::createTempDirectory.

Are you sure you don't have any restrictions with your TMP folder?

But that would mean that you are probably running your CI tests in a non standard way, with admin rights or special settings for the virtual machine.

We just use the GitHub-hosted Windows runners, without any special settings.

Contributors with a normal setup (and not running as administrative user all the time locally) should see the same issue as me.

I should be able to get a similar setup. I'll have a look at it.