This is an issue

You should add in the description what bubble up means.

Example code has missing the code for count(aNumber), so some people like me didn't implemented, also add something on the description on how to implement the count method.

All use of Test.expect should be changed to Test.assertEquals.

And more importantly, the tests should show what it's trying to construct/test, so it's easy to see what is expected.

Guess it's not going to be done anyway. Closing.

Done. isPrime is not required anymore to pass the kata. Also random testcases were added.

I would consider this correct and desirable, rather than an issue.

Returning a number because you can is not good programming. The result is always a function in x, represented as a string.

For "practical use" you can try this one: http://www.codewars.com/kata/how-many-are-smaller-than-me-ii
;-)

Yep, you're right. I designed it so that people both implemented the isPrime function and used it in checkGolbach. And the first tests make sure that the first function works well. Maybe I should have given more freedom to people to choose the way they wanted to determine the primality (like using a sieve or something like that)
I might consider removing the validations for isPrime and let people implement checkGoldbach the way they want, but would need to make sure not to affect the solutions already sent.

No feedback. Tests are fine. Closing issue.

Expects a String result even when a number would be a logical result

isPrime function is not required for calcuting the prime pair for Goldbach's Conjecture, had to program is prime just to pass the specs

Nice kata.

Nice kata.

In your test cases, when you remove random numbers, you just remove one value, not ten. Check the for loop generating the values.