Ad
  • Default User Avatar

    Yeah my nickname isn't the easiest xD

    well at least you know that ;)

  • Custom User Avatar

    Yeah my nickname isn't the easiest xD And thanks for spotting the error.

  • Default User Avatar

    fixed. closing the issue.

    thanks @dfhwzwe

  • Custom User Avatar

    FTW found a bug in the random test verification method. I will let him verify and resolve this issue.
    ut-actual comparison while result was set in ut-actual-numeric.

  • Custom User Avatar

    I've just tried now and it seems ok. I didn't understand what was the problem?

  • Custom User Avatar

    Could you check now?

  • Custom User Avatar

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

  • Default User Avatar

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

  • Custom User Avatar

    I Think you're wrong. I've controlled it in a fork, and it' not as you say. Then I tried the attempt tests from the trainer, printing first cut and then the result my function returns, and here is a sample of what I get:

    00000640+
    00205121+
    Testing                                                                         
    Log
    00000194+
    00018916+
    Testing                                                                         
    Log
    00000583+
    00170237+
    Testing                                                                         
    Log
    00000598+
    00179102+
    Testing                                                                         
    Log
    00000711+
    00253117+
    ...
    You have passed all of the tests! :) 
    

    What makes you think that?

  • Default User Avatar

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

  • Custom User Avatar

    Hi,

    Seems you're doing java. more than 1300 completions in java, so I'd rather guess the problem is on your side.

    Seems too that you're "rather new" to cw, so here are some general guidelines about the comments:

    • Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
    • Suggestions: well, I guess that part is clear
    • Question anything else that is related to you having a problem solving a kata -> that's you, currently.

    When you post issues:

    • provide ALL the useful information:
      • language
      • input
      • outputs (actual, expected) when relevant
      • error message when relevant
    • check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
    • if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)

    When you post a question: well, most of the above apply too x)

    When you post code, use proper github markdown, so that it's readable.

    And for your current problem, did you check what are the inputs/outputs to try to debug your code on your own? Especially, check that you don't use any global/static variable that could mess up your code, if you recieve a string composed only from whitespaces (unlikely case, but... That's a beginning).

    Cheers

  • Default User Avatar

    Hi.

    I think randomTest are broken.

    i.e.:
    <expected:<[]> but was:<[yfyulrsywxymicxctognypg]>
    <expected:<[]> but was:<[vxwxqxdrgpnzcpimpqtygxgv]>