public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3784] New: should dejagnu be replaced by PyUnit?
Date: Fri, 22 Dec 2006 15:32:00 -0000	[thread overview]
Message-ID: <20061222153241.3784.cagney@redhat.com> (raw)

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?

-- 
           Summary: should dejagnu be replaced by PyUnit?
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cagney at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=3784

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2006-12-22 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 15:32 cagney at redhat dot com [this message]
2006-12-22 17:00 ` [Bug general/3784] " cagney at redhat dot com
2006-12-22 21:13 ` scox at redhat dot com
2007-01-08 12:10 ` cagney at redhat dot com
2007-02-22 15:38 ` cagney at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061222153241.3784.cagney@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).