Good suggestion. I'll fix that up.

Ah, you mean because I make a setSecret() and getSecret() it doesn't demonstrate the value (if you have a setter and getter why not just have a property? Would you find the kata more interesting if getSecret() did something besides return the secret, like masked part of the secret (thinking about SSN's or something)?

I'll ponder a way to make it a more interesting application to demonstrate value. Good feedback.

Hey everyone, I added to the tests to help refine the acceptance criteria. There are now tests to make sure that multiple secret holders can be created and used. As well as that the secret is truly copied.

I can't say that it's super practical, however I think its worth knowing.
It really just demonstrates an application of closures. But doing it correctly requires understanding javascript scoping pretty well.

I would suggest improving the instructions slightly. Instead of "Add the two digits" say "Add the two digits of the sum"

This clarification would have saved me a lot of time.

Otherwise, solid Kata.

Yeah, if you read Javascript: the Good Parts by Douglas Crockford, his recommendation is that for built-in javascript types its best to always use literal notations.
i.e

var foo = 5; //Good
var foo = new Number(5) //Bad

var obj = {} // Good
var obj = new Object() // Bad

As a simpler mechanism than clans I would like to be able to star users like github or have "friends" like facebook.

My use case is that I've invited several co-workers to code wars. When they sign up, I want to compete with them and try to beat challenges they've completed.

We've already started doing this during lunch breaks, but it appears impossible to track them down on CodeWars

More Descriptive Javascript Compilation errors would be very helpful.