Ticket #1302 (new bug)
PIR todo() is frequently misused
Reported by: | Util | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | testing | Version: | 1.8.0 |
Severity: | medium | Keywords: | test more pir todo |
Cc: | Util, kid51 | Language: | |
Patch status: | Platform: | all |
Description
In pure PIR .t tests that use the test_more harness, the todo() function either:
- is constant todo(0, ...), preventing "unexpected success" info from ever printing, or
- is constant todo(1, ...), causing confusing "unexpected success" to always happen on TODOed platforms, or
- is conditioned todo($I0, ...), causing duplication of code or inability to use is() and friends.
This is a result of the todo() function's documentation and API.
Further analysis to follow...
Attachments
Change History
Note: See
TracTickets for help on using
tickets.