Skip to content

"Kumite was published with failed tests" even though all tests are succesful #317

Open

Description

@FranzMartyn

Describe the bug

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)

  1. Create a Kumite in Groovy (org.junit.Test should be automatically imported in the Tests Cases)
  2. Write tests using assert
  3. Publish it
  4. Edit the Kumite
  5. Replace import org.junit.Test with import org.junit.jupiter.api.* and import static org.junit.jupiter.api.Assertions.assertEquals

Expected behavior

The yellow message in Screenshots to not appear

Screenshots

image

Browser

  • OS: Windows 10 Pro 22H2 (Build 19045.4651)
  • Browser: Chrome
  • Version: 127.0.6533.120 (Official Build) (64-Bit) (cohort: Stable)

Additional context

Kumite

Activity

  1. interrupt-routine commented on May 27, 2026

    @interrupt-routine

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions