On 12 Jun 2005 10:14:50 GMT, Jorgen Grahn <[EMAIL PROTECTED]> wrote:
[regarding module unittest]
> What's the best way of creating a test.py which
> - aggregates the tests from all the test_*.py modules?
> - doesn't require me to enumerate all the test classes in test.py
> (forcing each module
"Robert Brewer" <[EMAIL PROTECTED]> wrote:
> Anyway, use normal os.walk() calls to gather the files which start with
> "test_"; then use the TestLoader.loadTestsFromName method to instruct
> unittest to test them as a group.
Hi Robert,
this makes much more sense; os.walk and TestLoader.loadTests
"Jorgen Grahn" wrote:
> I have a set of tests in different modules: test_foo.py,
> test_bar.py and so on. All of these use the simplest
> possible internal layout: a number of classes containing
> test*() methods, and the good old lines at the end:
> >>
> >> if __name__ == "__main__":
> >>
"Bengt Richter" <[EMAIL PROTECTED]> wrote:
> On 12 Jun 2005 08:06:18 -0700, "George Sakkis" <[EMAIL PROTECTED]> wrote:
>
> >I had written a script to do something close to this; currently it
> >doesn't do any kind of aggregation, but it should be easy to extend it
> >as you like. What I don't like
"Jorgen Grahn" wrote:
>What's the best way of creating a test.py which
>- aggregates the tests from all the test_*.py modules?
You might want to check out the test runner in Zope 3
(svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/app/testing)
It aggregates test reporting, does code coverage,
On 12 Jun 2005 08:06:18 -0700, "George Sakkis" <[EMAIL PROTECTED]> wrote:
>"Jorgen Grahn" wrote:
>
>> I have a set of tests in different modules: test_foo.py, test_bar.py and so
>> on. All of these use the simplest possible internal layout: a number of
>> classes containing test*() methods, and th
Jorgen Grahn wrote:
> I have a set of tests in different modules: test_foo.py, test_bar.py and so
> on. All of these use the simplest possible internal layout: a number of
> classes containing test*() methods, and the good old lines at the end:
> if __name__ == "__main__":
> unittest.main()
"Jorgen Grahn" wrote:
> I have a set of tests in different modules: test_foo.py, test_bar.py and so
> on. All of these use the simplest possible internal layout: a number of
> classes containing test*() methods, and the good old lines at the end:
>
> if __name__ == "__main__":
> unittest.m
"Jorgen Grahn" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>I have a set of tests in different modules: test_foo.py, test_bar.py and so
> on. All of these use the simplest possible internal layout: a number of
> classes containing test*() methods, and the good old lines at the end: