This code is simple, made up by just a single class, but we can still make it much more readable by properly indenting the variable names, datatypes and "=" character. Adding whitespace to vertically align each part of the similar lines, it becames very clear to the reader the pattern followed by all the variables of the class.

I learned something new today so this kata was definitely worth it.

I thought the same thing, but there is a solution

I must be missing something, you can't name a variable a type? That's a reserved word

JS: Default problem of twoOldestAges the code is

C#: Tests of a random nature there are not

Fixed this issue, thanks.

The values don't matter.

But the Assert.AreEqual with the GetValue method test whether the values match yours exactly, even if present. I highly suggest removing all the Assert.AreEqual lines, and removing the GetValue method altogether. Only keep the Assert.IsTrue checks above them. Do this for both the sample tests and submission tests.

While at it, include a string message with every assertion, like Assert.IsTrue(/* blah blah */, "Expected bool to be defined");.

The tests now still compile even on error, which is good. This resolves my suggestion, but introduces an issue that I will raise in a different comment up.

You are right, thanks. I will try to be more sensitive about this issue.

When the language is broken and you use terms like "variable key" and "this keywords" it becomes very difficult to figure out whether there are significant details in that wording or not. A kata description is published text, similar to a news article, it can't be THAT broken. (It's also technical text, and words have meaning.) Also, avoid using Notes, put the information in the text, no idea why so many kata do that for no reason as it looks very bad. The solver should be putting their energy into the problem, not into second-guessing grammar or wondering whether the tests/overall kata are of similar quality - a kata asks the solver to trust the kata.

Task

Define the following 13 variables:

bool char sbyte byte short ushort int uint long ulong float double decimal

The type of each variable must be the same as the name.

The values don't matter.

Examples

bool bool = false;
char char = '\0';
sbyte sbyte = 0;
...

This is because my native language is not English, I am writing by confirming it with translation.

I am open to suggestions; if you point out any mistakes or missing parts, I can correct them.

Is the description in super broken english or is it supposed to be like that?

Re-published kata, thanks for your feedback.

Probably my C# knowledge is lower than yours; I used ChatGPT to create test cases, and there is no solution found within the test anymore.

By the way its my first created kata. So trying to learn more..

This was a situation that I was also aware of, it was fixed. Thanks ^_~