You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Kumite was published with failed tests" even though all tests are succesful #317
I had to do some changes to a kata translation. The link to the kumite is in Additional context. Previously, I used groovy's built-in assert statement which I replaced with org.junit.jupiter.api.Assertions.assertEquals. I also changed the @Test annotations from org.junit.Test to org.junit.jupiter.api.Test.
To Reproduce
(I'm not sure whether this might work, but this is what I did)
Create a Kumite in Groovy (org.junit.Test should be automatically imported in the Tests Cases)
Write tests using assert
Publish it
Edit the Kumite
Replace import org.junit.Test with import org.junit.jupiter.api.* and import static org.junit.jupiter.api.Assertions.assertEquals
this happens when you modify a translation that has already been approved. editing approved translations has no effect on the kata and they cannot be re-approved. the only thing it does is making tracking down the history of versions very confusing, so editing approved translations should be disallowed to begin with.
Activity
interrupt-routine commentedon May 27, 2026
this happens when you modify a translation that has already been approved. editing approved translations has no effect on the kata and they cannot be re-approved. the only thing it does is making tracking down the history of versions very confusing, so editing approved translations should be disallowed to begin with.