Very interesting kata!

If more than one item you could produce would bring you equally close to the desiredRatio, return the lowest index amongst the equal options. (E.G. if producing item 5 or 7 would both bring you equally close, return 5).

The tests expect the opposite.

Random tests are unacceptable: they're all of the form actualStock[i] = desiredRatio[i] + n for certain n.

Everything seems to be working correctly now (using C# 8.0 at least).

I agree. I don't know what TestTools is, exactly. In order to work on this offline, I had to rewrite the tests to use CollectionAssert instead. Katas should not have external dependencies that aren't provided. Maybe TestTools is something that Codewars offers, but I just can't locate.

The following warning appears when attempting in C#: "tests/Fixture.cs(150,41): warning CS0168: The variable 'e' is declared but never used". Also, it's not possible to just copy and past the tests into visual studio because they rely on TestTools.

Think this Kata is broken, in C# atleast, it is saying that my exceptions do no get thrown, tested in visual studio with the same input and they do indeed get thrown, how can we fix this?

You do not need the 'return' for Ruby in this case, though. The == operator will always give a return value of true or false.

Terrible explanation. So much text to read and at the end of it you just realized that you don't now what to do. Examples shout to be improved as this kata is more like guessing than actual coding. Overally quite an interesting and difficult to pass.

ther's an issue with the random tests on c# can u check please

Approved

(Added random tests.)

There was no requirement to check input, so this solution is optimal.

nice and interesting kata, suggest to add one random test to avoid cheating.

Very nice idea and very good kata! In my opinion ready to been approved!
Thanx!
Have a look at my katas if you like!

Description could be clearer and more precisely.