Bug 3784 - should dejagnu be replaced by PyUnit?
Summary: should dejagnu be replaced by PyUnit?
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 2234
  Show dependency tree / graph
 
Reported: 2006-12-22 15:32 UTC by Andrew Cagney
Modified: 2007-02-22 15:39 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2006-12-22 15:32:41 UTC 
dejagnu has the advantage of working well with serial I/O programs (due to
expect) but the disadvantage of being yet another testing framework to learn and
the test model isn't very consistent when compared to JUnit.

PyUnit has the advantage of being shared with dogtail's test framework, being
similar to JUnit in its approach, but being an unknown when it comes to handling
serial I/O (and some people dislike python more then tcl :-)

How good is PyUnit at handling seerial I/O?
Comment 1 Andrew Cagney 2006-12-22 17:00:41 UTC 
Please debate :-)
Comment 2 Stan Cox 2006-12-22 21:13:44 UTC 
or perhaps pexpect (http://pexpect.sourceforge.net/)
Comment 3 Andrew Cagney 2007-01-08 12:10:19 UTC 
Another option would be to set up a simple JUnit based framework.
Comment 4 Andrew Cagney 2007-02-22 15:38:27 UTC 
frysk.expunit added; deajgnu removed.
Comment 5 Andrew Cagney 2007-02-22 15:39:00 UTC 
changes committed