#1951: t/dynpmc/os.t incorrectly uses system-specific error strings
----------------------+-----------------------------------------------------
Reporter: doughera | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: testing | Version: 2.11.0
Severity: high | Keywords: gci, cage
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Comment(by doughera):
Replying to [comment:3 jkeenan]:
> Would it be plausible to try to capture the system's own output of these
(bad) commands and use that as the basis of the pattern which the test
tries to match? That way, we wouldn't be trying to match a hard-coded
string.
I'm not sure it's important to test the exact error message in these
cases. I'd think it would be sufficient to test that operations that
should succeed do succeed, and that operations that should fail do fail.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1951#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
