Min and Max just return single values, so you need put them into array.

Yes, but my point was that this isn't best practice.. just clever.

the description says the input will be all positive integers

Good, but if they were to pass negative numbers as an input and it would fail..

outdated and author no longer active

The it block of the random tests should be it "Testing #{arr.inspect} and #{fun.toString()}", ->

Otherwise, the output looks like this

Testing 4,25,11,29,12,-3,10,26,-6,0,1 and function (v) {
            return v === 4;
          }

Done

Added to sample tests. Not sure what arr.inspect for it blocks means though, something I've missed in the test framework?

• arr.inspect for it blocks should be used

• Sample tests are missing corresponding blocks

• Unnecessary assertion at header of tests should be removed

• Can you make description language-agnostic in the meantime?

At least, it lacks random tests

This is why I like code reviews, you get to weed out your own bad habits

Cleaned it a bit

• Missing it block in fixed tests

• Sample tests is also missing describe && it blocks (wise approach would be to copy fixed tests into sample test section)

• it block for random tests should display the input properly using JSON.stringify

Rejected due to

• No random tests

• Using Test.expect

• Description MC

• Sample tests are not in-line with other languages

When I was trying to use this method it said me that it's wrong. WTF? 🤬