Ad
  • Custom User Avatar

    Typescript random tests seem to incorrectly fail even when they are correct, basic tests however work as anticipated... You can see in the examples below that they are all expecting a value of 1:

    Basic tests
    Testing for [1, 2, 3]
    Testing for [4, 1, 1, 1, 4]
    Testing for [2, 2, 2, 2, 2, 2]
    Random tests
    Testing for [7, 3, 4, 6]
    expected 504 to equal 1
    Completed in 2ms
    Testing for [8, 4, 7]
    expected 224 to equal 1
    Testing for [9, 2, 1]
    expected 18 to equal 1

  • Default User Avatar

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

  • Custom User Avatar

    Please put a note which day is considered to be counting as "until Christmas" (25th of December) as in some cultures - although even there technically not 100% correct - some may think intuitively of the 24th of December as "until" Christmas, since in their culture this is the day of the peak of the celebration.

    Also, as already mentioned in another comment, the instruction "She will start counting from the first of December." is wrong, as she begins counting from the 26th of December.

  • Custom User Avatar

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

  • Default User Avatar

    In C, the input array should be const qualified, as the user is not supposed to mutate it

  • Default User Avatar

    Note that your boss is in the room (boos), their score is worth double it's face value (but they are still just one person!).

    So, how do I know who's the freaking boss?

    Oh yeah, and I'm having the same random tests issue as everyone

    My issue is getting a little bit out of hand...

  • Custom User Avatar

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

  • Default User Avatar

    I am new to codewars and was curious if there is a way to compare solutions based on efficiency (time/space)?

  • Custom User Avatar

    It's a great kata but the description has to be clearer. That's why the satisfaction rating is so low.

  • Default User Avatar

    As others have mentioned, this description needs to be updated to explain what is actually expected from solutions. For one thing, the Kata never explains what a "Super Smash" is, and it's only by reading other user comments that I was able to determine that this occurs when there are open doors on both sides of the street at the same position. Also, since it is never specified in the description, I assumed that you are supposed to be riding from left to right, and so you are only concered with cars that are at or after the given starting position, x, but many of the test cases seem to expect you to also check the status of cars before your starting position. If you assume that you are instead riding from right to left, then even more test cases fail. In addition, if there is "an open door of a car facing the same way you are going" that comes after "an open door of a car facing you", should the return value for the former collision be given? The description doesn't specify, so I would assume that you're concerned with the first collision, but this doesn't seem to be consistent with all of the test cases. Either the test cases need to be fixed, or the description needs to be corrected, because right now the two are inconsistent with each other.

  • Custom User Avatar

    Try my solution for a couple of times and you will get undefined array key 14, on line 16.
    I think there is something wrong with the randomly generated test cases.
    This will be the first time I will try to fork and locate the problem :D :D

  • Custom User Avatar

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

  • Custom User Avatar

    "All letters will be lowercase and all inputs will be valid"

    Random Tests can lead to Kata.high(""), a warning would be appreciated.

  • Custom User Avatar

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

  • Default User Avatar

    JavaScript

    only intermittently fails this solution

    by not always producing tests such as these

    [
       "~~~~_",
       "~~~__",
       "~______",
       "~~~~~~~__~________",
       "~~____~~~~~~~__",
       "_____~",
       "_________~~",
       "_~~~~"
    ]
    

    where for each expected 'Throw Up' to equal 'No Problem'

  • Loading more items...