See https://www.codewars.com/kata/562086bbaacc2b4d13000047/discuss/javascript#657d1ac4dc8017ba924dd64e

The migration from the old expect utility to chai introduced this regression. I'm surprised there aren't any safeguards for expect calls that are never completed. There were a few other no-op expect calls that this report uncovered. Thank you.

P.S. I initally reported this comment, because it read like a person just copying their solution into chat. In the future please mark the comment as an issue and reference the submission without publicly pasting the code.

No clue why that solution passes:

// Validate Anakin's hint.
var hint = String(anakin.hint(colors.slice()));
it('Anakin should provide a valid guess', function() {
  if(colorOptions.indexOf(hint) >= 0) {
    chai.assert(true);
  } else {
    chai.expect(false, 'Invalid hint! (' + hint + ')');
  }
});

See my comment on your solution and the issue raised in the discussion board - yes, this passes the tests, but I'd argue that this just means that the tests aren't doing what they should ;)

Props for finding this, but I feel like this is more of an exploit than an actual solution as it violates Condition 2 ("Anakin's hint must be a droid color."). I've raised this in the discussion and suggested that this should be enforced more strictly. I do admire the cheek though ;)