these are not classes, they are the names of the tests groups

The class name should be BasicTests and RandomTests, not Basic Tests and Random Tests according to Ruby Style Guide

Also why is Basic Tests spelled Baisc Tests

I see what you mean. I am initializing the total of the ascii values to 0, so if there's no input, that zero never increases and eventually gets converted to a space. So if there's nothing but that space, I should return an empty string. Otherwise, spaces resulting from zeros should remain in the result.

I think you've read that failure message wrong, it's mildly confusing (cause it's making an attempt at showing it inlined in the message but it just comes out as badly spaced and it doesn't tell you it's doing it, when it could simply use a string literal), and you're looking at a space in the converted string, not the input.

Return a empty string if the input is empty

(an btw)

I don't see why there's a need for that special case though. SPECIAL case, not edge case, because that's not included in the rules section.

... I also don't understand why "printable" or cp1252 are mentioned, and I find the wording "space and other printable characters" really strange as space arguably is not printable and then one may wonder what else that kinda isn't printable might show up. except, none of it matters anyway

Instructions should mention that in the case of a single space, a zero-length string should be returned instead. A space is not "empty" input.

Fixed. Added a reference to the function

Why did you mark it as a issue? It should be suggestion not issue

This needs corner cases included in tests.

Specifically, the case where v2[0]==v1[0] is not tested for. I was able to pass the tests with a solution that would fail here

Don't mark unsolved issues as solved:

• Result should be handled by using approximate equality instead of rounding
• Spare us the input validation. This is documented.
• If you don't check, possibly by testing intermediate results, that solvers use a particular method, the description should not positively say "using the shoelace formula". You can describe possible methods, but kata generally test results, not methods.

fixed, also the inputs aren't floats

Fixed

• Spare us the input validation. This is documented.
• If you don't check, possibly by testing intermediate results, that solvers use a particular method, the description should not positively say "using the shoelace formula". You can describe possible methods, but kata generally test results, not methods.
• Calculating the area of a triangle is not Hard. It is not a 5kyu task ( that problem will solve itself ), and it should not be described in the kata title as hard, which raises expectations that are bound to be disappointed, and does not fit with other problems on the site. Optimal Transportation is Hard. Transpiling to BF is Hard. Area'ing a triangle is not.