Mihály Verhás

> enhance all disabling extensions (where this makes sense) to check for the presence of @Until and, if it's found, forward the attributes to the usability class I disagree. Instead...

What's the upside of the annotation over this one-liner: ```java assumeTrue(LocalDate.now().isBefore(2022,1,1), "An optional reason"); // or assertTrue if you want the test to fail, not abort ```

Hm, I guess, you could say that this assumption/assertion is meta - it's not really an assertion or assumption that is part of the test and therefore should be moved...

> But maybe the annotation is too esoteric to be included in JUnit Pioneer 😄 . Not at all! Our `@ReportEntry` annotation uses the same reasoning (report entries are meta...

The easiest and (in my opinion) obvious solution would be to make this behaviour configurable. We could introduce an enum, e.g.: ``` enum ExecutionPhase { BEFORE_EACH, BEFORE_ALL } ``` The...

JUnit does not register extensions from parameter annotations. Meaning this: ``` @Test void asContentString(@ResourceRead("sub/anton.txt") String content) { ``` does not work.

[We are just too slow, it seems.](https://github.com/khmarbaise/resources-extension)

That last one kind of sounds like could be solved with a spy from Mockito? Something like: ```java static T spy = Mock.spy(new T()); @AfterAll static void assertNoInteractionsWithEquals() { then(spy.equals(any())).shouldHaveNoMoreInteractions();...

To assert interactions with objects, we'd need to do something invasive - like mocking or a Java agent. That's the hard part (to me). If we have that, then the...

This ticket is now indefinitely on hold, contingent on sonar implementing the new feature (analyze external PRs).