I don't think that it's one of the best solutions: here filter is called two times, so it's likely that you iterate two time on input, which is unnecessay. This can be solve with a vanilla for loop & one if.

Really clever

In the constructor with args, no need to set Volume&Surface since they are already calculated using Side setter....

LOL! I love people like this!!

Here also, putting a range in as you did, 3070, 1530, runs my tests correctly (on my own node server), but here the expected results begin with a value lower than my starting value.

same

It's during a getPrimes test. Maybe I missed something but the expected sequence was wrong (for instance another test, when I save&attempt, I log start&finish parameters; given 3070 & 1530, the test fails asking for an expected sequence begining with : "Test Failed: Expected: 1531,1535,1537,1541,1543,1547,1549,1553,1555,1559,1561,1565...." that does not contains only primes.

What code did you use to have this occur? I just ran isPrime against 3025 and it fails out correctly.

Are you sure the tests are still good ?
For 5006 and 3018 I got an expected result begining with "Test Failed: Expected: 3019,3023,3025,3029,3031...."
It contains 3025 and it's of course not a prime number...