Ad
  • Custom User Avatar

    JS tests print AFTER assertion

    assertion fails -> exception -> print never happens because exception exited the function early -> no information given to solver what's wrong

    the python tests are also written this way but that test framework doesn't exit early on failed assertion (it should though, and it could conceivably change that behaviour)

  • Custom User Avatar

    the test code intended to print out failure messages but was written in an incorrect way that used to "work" but now doesn't (specifically there were console.log's after assertions - but a failed assertion raises an exception and thus exits early and skips code after it)

    the tests have been updated, they'll now tell you what they don't like.

  • Custom User Avatar

    so there are 5 tests total. The one I'm failing is the 'validity' test.. Any information on what this is expecting?

  • Custom User Avatar

    in JavaScript:

    Passing all 4 tests(10k passwords generated, testing lengths, testing inequality, testing character count)
    proceeded by 1 fail saying: "Invalid passwords generated!: expected false to be true"

    Is there something I'm missing here?

  • Custom User Avatar

    Not a kata issue, there are problems with your solution.

  • Custom User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Custom User Avatar

    I'm simply used to calling std:: all the time. It helps me know that I'm not using a regular function.

  • Custom User Avatar

    You could use this "using namespace std;" so you don't have to do the std:: all the time