'looks like you solved it'
Both in sample and final tests, that test is like this:
Test.expect(largestPairSum([-10, -8, -16, -18, -19]) === -18 , "Sum should be -18");
Click reset if you see other thing in sample tests.
I just did the js one and the test case was
Test.expect(largestPairSum([-10, -8, -16, -18, -19]) === -16 , "Sum should be -18");
Which is obviously wrong and when you hit attempt, it knows it should equal 18. 16 should be changed to 18 in the js texts case.
I was not careful and decided that we need the sums of numbers that are nearby, but the solution worked, lol ))
it seems not enough tests
Random tests are not similar to edge cases tests
So it's the same issue as reported below, 3 weeks ago.
and the language is?
Bad testing, need an edge cases.
One of my solutions was wrong, but there is no test cases for descending array like [3, 2, 1] and wrong solution works
Forked ruby translation kumited, including random tests -- please check and approve (note: author is inactive)
Python translation with random tests
No random tests for JS
or u can save the calculations