From: SourceForge.net <no...@so...> - 2003-04-21 20:29:41
|
Bugs item #725253, was opened at 2003-04-21 16:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=725253&group_id=10894 Category: 34. tcltest Package Group: 8.5a0 Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Don Porter (dgp) Summary: customMatch attempt follows codeFailure Initial Comment: When an unexpected error happens in a test, the return code (1) does not match the expected return codes (0 and 2 by default), however, result matching is still attempted against the result. This can be trouble when the -custom match is in effect, and it expects a certain format of result (say, a valid list), which is not met by the error message. Fix for this, is to not bother checking the result match, when an unexpected return code is seen. The unexpected return code is already enough to make the test fail, and one failure with a good message is better than multiple failures that cause confusion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=725253&group_id=10894 |
From: SourceForge.net <no...@so...> - 2003-04-21 20:44:45
|
Bugs item #725253, was opened at 2003-04-21 16:29 Message generated for change (Comment added) made by dgp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=725253&group_id=10894 Category: 34. tcltest Package Group: 8.5a0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Don Porter (dgp) Summary: customMatch attempt follows codeFailure Initial Comment: When an unexpected error happens in a test, the return code (1) does not match the expected return codes (0 and 2 by default), however, result matching is still attempted against the result. This can be trouble when the -custom match is in effect, and it expects a certain format of result (say, a valid list), which is not met by the error message. Fix for this, is to not bother checking the result match, when an unexpected return code is seen. The unexpected return code is already enough to make the test fail, and one failure with a good message is better than multiple failures that cause confusion. ---------------------------------------------------------------------- >Comment By: Don Porter (dgp) Date: 2003-04-21 16:44 Message: Logged In: YES user_id=80530 fixed in tcltest 2.2.3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=725253&group_id=10894 |