Menu ▾ ▴

#1303 Should test interactive tcl commands using expect

obsolete: 8.1
closed-invalid
Don Porter
34. tcltest Package (79)
5
2002-03-24
2000-10-26
Anonymous
No

OriginalBugID: 3747 RFE
Version: 1.3
SubmitDate: '1999-12-01'
LastModified: '2000-02-10'
Severity: LOW
Status: UnAssn
Submitter: jenn
ChangedBy: hobbs
OS: All Unix
FixedDate: '2000-10-25'
ClosedDate: '2000-10-25'

We should use expect to test tclsh and wish interactively. Currently, there are no tests for this, and different commands are available when you start up an interactive shell (e.g. history).

Discussion

  • Donal K. Fellows

    Donal K. Fellows - 2000-12-12

    I suppose you could make the availability of Expect into a constraint...?
    It isn't a good idea to blanket require it though, since many installations of Tcl don't have Expect (yet!) and we want the test suite to be as widely runnable as possible.

     

  • Donal K. Fellows

    Donal K. Fellows - 2001-02-07
    • labels: 104252 --> 34. tcltest Package
     

  • Jeffrey Hobbs

    Jeffrey Hobbs - 2002-03-22
    • assigned_to: nobody --> dgp
     

  • Don Porter

    Don Porter - 2002-03-24
    • status: open --> closed-invalid
     

  • Don Porter

    Don Porter - 2002-03-24

    Logged In: YES
    user_id=80530

    This should not be necessary. tcltest 2 offers [interpreter]
    to give you the executable name of the current harness.
    Use that to [open |[interpreter]] another copy and
    interact with that. main.test includes examples of this.