Блог пользователя hydroshiba

Автор hydroshiba, история, 5 лет назад, По-английски

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.

  • Проголосовать: нравится
  • -30
  • Проголосовать: не нравится

»
5 лет назад, скрыть # |
 
Проголосовать: нравится -7 Проголосовать: не нравится

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.

»
5 лет назад, скрыть # |
 
Проголосовать: нравится +18 Проголосовать: не нравится

I got you covered: CF Debug

»
5 лет назад, скрыть # |
 
Проголосовать: нравится +18 Проголосовать: не нравится

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.