Test framework: Silent failure on bad "outcome" values
Bug #574141 reported by
Matt Giuca
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mars |
Fix Released
|
High
|
Matt Giuca | ||
Bug Description
The compilation testing phase of the Mars test framework accepts a parameter "outcome" which must be one of "succeed" or "fail". If any other value is given, it will currently silently treat it as "fail". It should be an error (like it is for other bad values in the MTC file).
This is particularly troublesome, as I have a habit of writing "outcome: pass", which is implicitly interpreted as "outcome: fail". (In fact, several MTC files contain "outcome: pass", and these will need to be fixed.)
Related branches
Revision history for this message
| Matt Giuca (mgiuca) wrote | #1 |
Revision history for this message
| Matt Giuca (mgiuca) wrote | #2 |
| Changed in mars: | |
| status: | Triaged → In Progress |
| status: | In Progress → Fix Committed |
| Changed in mars: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
While you're at it, enhance the documentation in this section. It is very confusing (what the difference is between "outcome" and "expect").