Ad
  • Custom User Avatar

    In many random tests, all my test rows match except for a few, e.g.

    correct answer:
    "'D...'" 9!  Xy14lmTDftz-
    YtlLqmJ3Q!  "Gli9..."
    
    my answer:
    "'D...'" 9!  Xy14lmTDft-
    zYtlLqmJ3Q!  "Gli9..."
    

    In this example, the last letter of line (n) is shifted to the beginning of line (n+1) compared to the reference solution.

    Can I assume that if "123\n4567" is a correct solution, then "1234\n567" is also a correct? Is there a rule to make the solution unique?

  • Custom User Avatar

    (python)
    If a test is not passed, result is displayed twice:

    1. nicely formatted: Expect/Actual
    2. unformatted: Actual/Expected
    Input text: 
    
    Hi, I am some text and I need to be arranged.
    
    Line length: 15
    
    * Correct answer: 
    
    Hi, I am some
    text and I need
    to be arranged.
    
    * Answer returned: 
    
    Hi, I am some 
    text and I need 
    to be arranged.
    : 'Hi, I am some \ntext and I need \nto be arranged.' should equal 'Hi, I am some\ntext and I need\nto be arranged.'
    

    Is it possible to display only 1)?

  • Custom User Avatar

    I want to see the EN DASH character in the text. To do this, I copy the dash character from the sample tests window and execute the following code in python:

    import unicodedata
    c = "—" # char copied from the sample tests window in browser
    print(f"Unicode-Name: {unicodedata.name(c)}")
    

    the python output is "Unicode-Name: EM DASH".
    As I understand the description, an EN DASH was used in the text. Can someone please explain what I am misunderstanding?

  • Custom User Avatar

    Python:

    passing all fixed test cases but no random test cases. Although it is probably because of my terribly-written, bug-riddled code, the random tests are impossible to debug. The strings are way too long, and it would be really helpful if there were some shorter random strings.

  • Custom User Avatar

    The test structure of both sample tests and actual tests need to be modified: it's calling user solution twice per test for no reasons.