Matthias Bünger

icon location Bonn, Germany icon location Loves #Java, #JakartaEE, testing, and documentation | Maven commiter | Became a (slow) runner (HM 2:26) after 3x cancer some years ago. | Listens to metal 🤘

Results 168 comments of Matthias Bünger

Upgrade Gradle and pipeline when Java 18 is supported

Java 18 is now supported by Gradle 7.5 according to the matrix

Provide annotation that a test currently fails by given circumstances

Just found: #468 (Abort tests if URL is unreachable) which also goes into this direction

Provide annotation that a test currently fails by given circumstances

I like the wording with `@Silenced`. Maybe we can use that in a way.

Create `@Flaky` extension

@nipafx @beatngu13 @Michael1993 and me talked about this on a team meeting you could not attending, so discussion needed :)

Simplify Gradle build

@aepfli @beatngu13

Set up modular integration tests

I vote for @sormuras to implement that 👼

Set up modular integration tests

link to #617

Set up modular integration tests

@beatngu13 Is this still relevant, when upgrading to Java 11 (in #627)

Set up modular integration tests

@beatngu13 wasn't that also done with #651 ?

Abort tests if URL is unreachable

> Thinking this over, I realized that I couldn't draw a clear boundary between uses cases for conditions (i.e. disabling a test) and for assumptions (i.e. aborting it). [JUnit says](https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/Assumptions.html):...