pyunit-interest

[Pyunit-interest] [Stupid Newbie Question] How do I use it?

[Ken C. <ke...@in...>]

So I've been studying XP and now it's time to start using it.  I'm using
Debian unstable so I apt-get python2.2-unit and python2.2-tk (by the
way, if the Debian maintainer for python2.2-unit reads this,
python2.2-tk should probably be in Recommends:) and I'm ready to rock
right?

Somehow I'm missing something...

Here's how I thought that I would use it:

I'm working on my project, time to run a test, bells and whistles are
fun so I'll use the tkinter gui

python2.2 /usr/lib/python2.2/site-package/unittestgui.py
mytests.MyTestCase

This is not exactly pretty but to make it better I understand I would
need to make a little scriplet or install unittestgui in the PATH or
something, no big deal.

However, I get an error because unittestgui can't find my test class. 
Of course... the current directory is not in sys.path so it's not
finding my module.

Anyway, it sure looks like I'm going to have to spend a little time to
either write a little executable for each of my projects, or spend a
little more time and come up with a more general solution that I can
just place in the PATH.

Has anyone already done this?  Or am I just missing the boat here?  Am I
misunderstanding something fundamental about the usage of unittest? 
Feel free to clue me in.

Ken Causey
ke...@in...

P.S. I'm not on the list so please be sure to respond directly to me as
appropriate.

Re: [Pyunit-interest] [Stupid Newbie Question] How do I use it?

[Ken C. <ke...@in...>]

Well, I guess I'll reply to my own post.

After posting my reply I noticed Patrick O'Brien's script and wondered
if I could start with that and make something that would use unittestgui
rather than the command line runner.  It seems a bit kludgy yet and I
haven't tested it thorougly, but here's what I've come up with that
seems to work:

ken@temp:~/temp$ cat testem.py
#!/usr/bin/env python2.2

__author__ = "Patrick K. O'Brien <<EMAIL: PROTECTED>>"
__cvsid__ = "$Id: testall.py,v 1.1 2002/03/14 23:10:20 pobrien Exp $"
__revision__ = "$Revision: 1.1 $"[11:-2]


import unittest
import unittestgui
import glob
import os

class Suite:

    def __call__(self):
        for filename in glob.glob('test_*.py'):
            module = __import__(os.path.splitext(filename)[0])

        suite = unittest.TestSuite()
       
suite.addTest(unittest.defaultTestLoader.loadTestsFromModule(module))
        return suite


suite = Suite()

if __name__ == '__main__':
    unittestgui.main('testem.suite')


Now that I paste this into an email I see it has a dependency on the
name of the module, but I suppose that could be fixed easily enough.

It seems to me that unittestgui needs to not restrict itself to strings
as it does.

Ken

Re: [Pyunit-interest] [Stupid Newbie Question] How do I use it?

[Ken C. <ke...@in...>]

If you don't mind I think I will reply to myself again, sigh.

As you may have imagined from looking at the code I just posted after
starting with Patrick O'Brien's code I went in several wrong
directions.  After sending off that email I happened to glance back at
Patrick's original code and realize that I had deviated quite severely
and unnecessarily from his methodology, so here's a version much more
like Patrick's and more sensible:

ken@temp:~/temp$ cat testem.py
#!/usr/bin/env python2.2

import unittest
import unittestgui
import glob
import os

def suite():
        for filename in glob.glob('test_*.py'):
            module = __import__(os.path.splitext(filename)[0])

        suite = unittest.TestSuite()
	suite.addTest(unittest.defaultTestLoader.loadTestsFromModule(module)
        return suite
    

if __name__ == '__main__':
    unittestgui.main('testem.suite')