Sorry for the typo... I think, I should really only use
the abbreviated "sf.net"... :-/
Dinu
----- Forwarded message from <gh...@da...> -----
Date: Fri, 19 Jul 2002 11:20:51 +0200 (CEST)
From: Dinu Gherman <gh...@da...>
Reply-To: Dinu Gherman <gh...@da...>
Subject: ANN: Pycotin 0.1, a Python Cocoa Test Interface for PyUnit
To: pyt...@py...,pyu...@li...
Hi,
for those who care, I've just released "Pycotin", a native
Cocoa GUI to PyUnit testing on OS X. It's been just born,
but looks verys promising. Please find the code plus two
screenshots in my Starship Python cabin:
http://python.net/~gherman/#Pycotin
Regards,
Dinu
PS: From the README:
Pycotin 0.1
Pycotin (Python Cocoa Test Interface) is a Cocoa GUI to
Steve Purcell's PyUnit test framework (1) on Mac OS X.
For now, its user interface is very much designed after
the existing Tkinter one (2), but that might slightly
change again.
Pycotin was developped from its author's personal frust-
ration with running (or rather not running) Tkinter on
Mac OS X as the only existing GUI for PyUnit. While it
might well be possible to make Tkinter run on this plat-
form, it was probably easier to write this little tool...
Basically, with Pycotin you can "open" Python files (with
extension ".py") and execute testsuites created in these
files with the "unittest" module of the Python 2.0 stan-
dard library. Right now Pycotin trys to import a function
named "suite()" or "makeSuite()" from an opened Python
module which it assumes to build and return a testsuite.
This can clearly be made much smarter, but also depends
on your habits as testsuite designer.
The test files in samples/ were shamelessly copied from
Steve Purcell's own original test cases for PyUnit 1.4.1
(just skipping the Tkinter ones for obvious reasons).
I added only one new file, "listtestsfail.py" which shows
a failing test, too.
Pycotin is in early alpha phase! Be not surprised to see
some buglets when dealing with paths containing blanks!
----- End forwarded message -----
|
