SuryaManikanta's blog

Bad Sample Test Cases
By SuryaManikanta, history, 3 years ago, In English

Yesterday, I gave codeforces round 801. I read first problem, I am the guy who expects clear problem statements any how I end up skipping first problem(I solved it later after contest dedicating 5 min for reading clearly and understand the problem),We do expect a clean and neat problem statement. Went ahead to solve problem B It's my fault I read the question wrong(Mike starts picking always from pile 1, I have not noticed that and solved for problem where Mike can start with any pile) My wrong observation code passed Test cases, So they can take some time and design sample test cases in a way such that many can clear their doubts about the problem from them(although I agree they can't show a way to solve the problem but adding few extra cases which don't direct to solution will definitely help readers/solvers to get good idea of the problem and avoids many mistakes.

  • Vote: I like it
  • +11
  • Vote: I do not like it

Comments Comments (6)
| Write comment?
»
3 years ago, # |
  Vote: I like it +2 Vote: I do not like it

I can relate to this issue, but I also think the sample cases can't always be good, and the sample cases are a part of the problem design (i.e. the problemsetter may design a misleading sample case intentionally to let some participants fall into the trap, this has been done in a few ptz camp problems already). so it's usually ideal to have a very clear sample case, but not always.

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

It is not enough! Authors must describe their solutions in statements!

→ Reply
  • »
    »
    3 years ago, # ^ |
      Vote: I like it +19 Vote: I do not like it

    Honestly, they should just link the editorials instead of the problems

    → Reply
    • »
      »
      »
      3 years ago, # ^ |
        Vote: I like it +14 Vote: I do not like it

      Yeah. Obviously, with source codes. As it seems, some people find it difficult to understand statements. Understanding editorials is even harder!

      → Reply
      • »
        »
        »
        »
        3 years ago, # ^ |
          Vote: I like it +3 Vote: I do not like it

        Actually, understanding source codes is still too hard IMO. I think they should provide us with a flowchart, a few lines of pseudocode, and then the source code with comments on every other line.

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

We all can take this as opportunity to improve our solving skills after all we are all here to become a good coder so if we can solve a problem without taking much logic from testcase we can learn more !!

→ Reply