hydroshiba's blog

Annoying testcases
By hydroshiba, history, 2 years ago, In English

Have you ever wanted to look for that wrong testcase in your past submission to debug your code, but instead saw this?


Or this?


And countless more...

Spoiler

You got the point. It felt so annoying when you just needed that one small testcase for debugging, but the box was way too small to show all of them and your precious testcase was unluckily the one that was buried deep down. It would be nice if there was an option to show the full test (in a new separate tab maybe) or just let the participants download the testdata once a contest ends. I've had to cope with this situation for 2 years, and I just hope that somebody will take a look at this.

Thanks for reading my blog.

  • Vote: I like it
  • -30
  • Vote: I do not like it

»
2 years ago, # |
  Vote: I like it -7 Vote: I do not like it

It should be good enough if the checker log prints that input data for the failed test-case. However, the log information is usually restricted to small data size. Tracing the test data file is more effective for debugging purpose when the failed test-case has large data size.

→ Reply
  • »
    »
    2 years ago, # ^ |
      Vote: I like it -8 Vote: I do not like it

    Yes, this should be a good idea. They can provide the complete test data input to download and debug it ourselves or either can print the failed test case input

    → Reply
    • »
      »
      »
      2 years ago, # ^ |
      ← Rev. 2   Vote: I like it -8 Vote: I do not like it

      I do not think that it is techically very difficult to add this feature for upsolving purpose after the contests.

      → Reply
»
2 years ago, # |
  Vote: I like it +18 Vote: I do not like it

I got you covered: CF Debug

→ Reply
»
2 years ago, # |
  Vote: I like it +18 Vote: I do not like it

The idea is that we learn to produce relevant test cases ourselves, not rely on the judges to show them. You won't be able to see the exact test case in a contest either.

→ Reply