In an evaluation with TESTed, when supplyin an empty string ("") in stdin, the system does not recognize this as an input.

[marcothijs]

In an evaluation with TESTed (for Python), when supplying an empty string ("") in stdin, the system does not recognize this as an input. You get the error: "EOFError: EOF when reading a line."

[pdawyndt]

Would stdin: "\n" work?

[marcothijs]

Yes, both "\n" or " " (space) do the trick.
In the tests.yaml:

• stdin: "\n"
  stdout: "Deze zin is geen pangram."
  • stdin: " "
    stdout: "Deze zin is geen pangram."

Result:

I was just surpriced to see that it didn't work with the empty string and wanted to let the team know.

Regards,
Marco

[pdawyndt]

It should have done the trick, so we should take this up as an issue that needs to be resolved.

Good to see that this workaround does the job. I would consider "\n" a different input then " " (which is transformed into " \n" by TESTed, to follow the POSIX standard convention that each line should end with a newline:

3.206 Line

A sequence of zero or more non- characters plus a terminating character.

So stdin: "" should have used "\n" (empty line), whereas stdin: " " uses "\n"as the line written to stdin (a line containing a space).

[marcothijs]

Indeed, "\n" is not the same as " " that gets translated into " \n". I had only used the space-input to show what the result in this exercise would be when an empty string (or nothing) would be entered (as the space is not visible on the screen). I've taken the stdin: " " out of the test-script. Thanks for providing the workaround, and for taking it up in the issue-list.