Re: cmd/tests: Add test for parameter detection

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=12408

Your paranoid android.


=== WNT4WSSP6 (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')

=== W2KPROSP4 (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')

=== WXPPROSP3 (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')

=== W2K3R2SESP2 (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')

=== WVISTAADM (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')

=== W2K8SE (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')

=== W7PRO (32 bit) ===
batch.c:214: Test failed: unexpected char 0x69 position 0 in line 77 (got 'if seems to not detect /c as parameter', wanted ' if seems to not detect /c as parameter')