| Ticket UUID: | 442663 | |||
| Title: | Simplify a couple of Tcl tests. | |||
| Type: | Patch | Version: | None | |
| Submitter: | mdejong | Created on: | 2001-07-19 06:09:32 | |
| Subsystem: | 34. tcltest Package | Assigned To: | hobbs | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2001-08-02 08:18:52 | |
| Resolution: | Fixed | Closed By: | hobbs | |
| Closed on: | 2001-08-02 01:18:52 | |||
| Description: |
Here is an old patch I found kicking around. While it does not actually change any functionality, I think it makes things much more simple. 2001-07-18 Mo DeJong <[email protected]> * tests/fCmd.test: * tests/parseOld.test: Simplify needlessly complex checks for the existence of test commands. | |||
| User Comments: |
hobbs added on 2001-08-02 08:18:52:
Logged In: YES user_id=72656 The fCmd tests were already updated at some point, and I more correctly did the skip on parseOld.test for testwordend. hobbs added on 2001-07-20 05:26:16: Logged In: YES user_id=72656 It might be better to do it via the testConstraints array, and place the constraints on the particular tests. This is actually just a few of many tests that would otherwise fail when not run under tcltest. The reason I like the constraints method better is that each run still has the same number of overall tests, and the summary output tells you the named constrainsts for what was skipped. andreas_kupries added on 2001-07-19 22:33:11: Logged In: YES user_id=75003 I remember that in a different place in the testsuite such checks were used to set a constraint which was then subsequently used by the affected tests to enable/disable them. mdejong added on 2001-07-19 13:09:34: File Added - 8592: tests.patch | |||
Attachments:
- tests.patch [download] added by mdejong on 2001-07-19 13:09:34. [details]