ItsDan
ItsDan
Thanks for the feedback and the suggestion to use metadata. It's definitely a more elegant approach in theory. After extensive debugging, the current implementation (using physically isolated tests with timing)...
This test is unable to run without waiting. If we want there to be no waits, somewhere we will need to document that this is untestable.
> Granted, it seems that the event will be fired without having any delays. I'm not sure if using an event in a non-junit testing environment is something that should...
The assertion `assert size of absorbed blocks is 1 with "Sponge should have absorbed 1 block"` will intermittently read absorbed blocks as `2` if I remove waits. My assumption is...
The test works fine from one side if we don't wait. I updated the test to test from one side as @APickledWalrus suggested, and removed the waits. If we need...
I've made the requested changes. I also added an assertion in the test block too. I'm still not 100% sure this can be truly considered testable. If you do consecutive...
I just find it strange that it runs fine in everything but Java 21. I'll consider figuring out turning it into a JUnit test, though I've never done JUnit tests...
> [...] Maybe some tests using substring and joining. I think substring and joining should be tested elsewhere. ie: `ExprSubstring.sk` should get created to test the substring. This file tests...