I'm personally curious about the need or desire to mention a method for C# or Java, when a.) this is relevant to any classical language, and b.) it should be obvious from the method call in the code example, in any case, the wording seems to suggest that C#/Java are the only language katas that are asking for a method, while any classic language is.

Though, this is made explicit in the code example, anyway.

Yeah, I guess you are referring to the C# translation. I'd like to just remove it, but it was created several years ago (unfortunately after the kata itself was out of beta), and any changes to it now would potentially break solutions that have already passed.

I would not select an option to allow translations for any kata that I made going forward.

oh okay. Out of curiousity, which language(s) did you try?

When I first made this kata, I thought it was better not to include tests in an attempt to encourage people to write their own, but that might not be what the community considers "best practices" now.

As for the errors, did they give any error messages?

Too easy, or...?

Will do!

I don't think it should ever have had a getColor() method in C#, but somebody else created the C# translation, and this has been out of beta for years, so making changes may cause issues for already accepted solutions.

Cool feedback. I'd be curious as to what sort of background someone might have where they are more familiar with data structure and algorithm puzzles than creating instances of a class with a default value in an OOP language.

As far as I know, the level of each kata is determined through feedback during its beta process, which for this particular one was more than 9 years ago. It's possible that criteria and other things have changed. The language versions and directions for testing, etc. seem to have.

Yeah, there weren't any sample tests added to the Kata when it was originally authored in Ruby, Python, and JavaScript. That wasn't a requirement at the time, and it went through the beta process into release about 9 years ago.

The Java translation was added after, by a different author, but must have also been before there was any requirement for sample tests.

Note: There are tests, which should give explicit messages for what fails, and any sample tests would likely be testing the same things.

If you didn't add them , why did you close the issue?

Because I authored the kata and explicitly chose not to add sample tests, which to me means that this is not an issue, but a suggestion.

Things change over time.

imo, if such changes are required, it would make sense to depricate any kata that have already gone through the beta process of being reviewed and approved, and have been live for several years. That way if original authors or the community would like to make such changes, they can release new kata or new kata versions.

In any case, while I disagree that this kata should have sample test cases, I'm in no position to prevent someone else from adding them.

Yeah, they don't have sample tests. When I authored the kata almost 10 years ago, I didn't feel they should have sample tests at this level. Feel free to write them yourself or remove the kata if you find that to be a genuine issue.

What does it mean for a kata to be out of beta?

It means that it has passed a review and commenting period and has been released.

Why did it show up as a potential kata for training with the existing issues?

If you feel there are issues, please provide details as to what they are, and of course which language you are experiencing them in. However, also keep in mind that with most of the katas, they are not in beta, and have been completed hundreds or thousands of times. It is often helpful to look at the details section which tends to show what the expected output is for a given input.

What you have reported here does not seem to accurately describe any issues with this kata from what I can tell.

How can I ensure that any given kata to train on will be void of issues in the future.

In my opinion and experience, generially eading the instructions is a good start. Taking some time to become familiar with the testing framework and writing some tests may also be helpful.

Best of luck to you!

This kata has been out of beta for almost 10 years. If you're going to open an issue, maybe have a look at the Description first.

Interesting observation!

Which language is this for?