Phillip J. Eby wrote:
> At 10:14 AM 1/22/2007 -0500, Jim Fulton wrote:
>> I'd rather let people use whatever framework
>> they want to do this and to control this from Python.
>
> The approach I suggested certainly allows that to happen,
I know. That's why I wouldn't object to it.
Jim
--
Jim F
At 10:14 AM 1/22/2007 -0500, Jim Fulton wrote:
>I'd rather let people use whatever framework
>they want to do this and to control this from Python.
The approach I suggested certainly allows that to happen, and if the
default loader is either unittest's default loader or setuptools' scanning
load
Phillip J. Eby wrote:
> At 01:11 PM 1/5/2007 -0500, Jim Fulton wrote:
>> Phillip J. Eby wrote:
>> ...
Why can't an entry point invoke a test loader itself?
This seems much simpler and more straightforward to me.
>>> Because that requires you to write code for something that can
>>> adequ
Hello all. I'm the primary author of nose. Michal Kwiatkowski was kind
enough to point me to this thread, and I wanted to chime in with a few
questions and answers. Apologies for pulling things from various parts
of the thread together, I didn't want to send multiple replies all
covering the same g
At 06:05 PM 1/8/2007 +, John J Lee wrote:
>On Mon, 8 Jan 2007, David Fraser wrote:
>[...]
> > So I need to go and code a test enumerator for py.test to discover tests
> > within eggs (which is possible)
>[...]
>
>Or (for new code) use nose, which AIUI is intended to be pretty much
>py.test impl
On Mon, 8 Jan 2007, David Fraser wrote:
[...]
> So I need to go and code a test enumerator for py.test to discover tests
> within eggs (which is possible)
[...]
Or (for new code) use nose, which AIUI is intended to be pretty much
py.test implemented within the unittest framework (plus whatever bi
Phillip J. Eby wrote:
> At 05:36 PM 1/5/2007 +0200, David Fraser wrote:
>> How would this work if for example, you're using an alternative testing
>> framework (like py.test) for your test?
> If I understand correctly, py.test simply won't be usable for this
> scenario, because it assumes tests ar
At 01:11 PM 1/5/2007 -0500, Jim Fulton wrote:
>Phillip J. Eby wrote:
>...
>>>Why can't an entry point invoke a test loader itself?
>>>This seems much simpler and more straightforward to me.
>>Because that requires you to write code for something that can adequately
>>be expressed through an existi
Phillip J. Eby wrote:
...
>> Why can't an entry point invoke a test loader itself?
>> This seems much simpler and more straightforward to me.
>
> Because that requires you to write code for something that can
> adequately be expressed through an existing configuration mechanism.
> *And* you hav
At 12:24 PM 1/5/2007 -0500, Jim Fulton wrote:
>Phillip J. Eby wrote:
>>At 08:46 AM 1/5/2007 -0500, Jim Fulton wrote:
>>>2. An optional 'tests' extra is defined. When creating test runners
>>> or dynamically loading distributions to load tests, any
>>> distributions listed in extra requires
Phillip J. Eby wrote:
> At 08:46 AM 1/5/2007 -0500, Jim Fulton wrote:
>
>> Here is a rough draft proposal for declaring tests in eggs:
>>
>> Introduction
>>
>>
>> Software packages should have automated tests. Consumers of
>> packages will often want to run these tests. Tools should
At 05:36 PM 1/5/2007 +0200, David Fraser wrote:
>How would this work if for example, you're using an alternative testing
>framework (like py.test) for your test?
If I understand correctly, py.test simply won't be usable for this
scenario, because it assumes tests are files first and modules secon
At 08:46 AM 1/5/2007 -0500, Jim Fulton wrote:
>Here is a rough draft proposal for declaring tests in eggs:
>
>Introduction
>
>
>Software packages should have automated tests. Consumers of
>packages will often want to run these tests. Tools should be able to
>do this automatically. T
David Fraser wrote:
> Jim Fulton wrote:
>> Here is a rough draft proposal for declaring tests in eggs:
>>
>> Introduction
>>
>>
>> Software packages should have automated tests. Consumers of
>> packages will often want to run these tests. Tools should be able to
>> do this automatica
Jim Fulton wrote:
> Here is a rough draft proposal for declaring tests in eggs:
>
> Introduction
>
>
> Software packages should have automated tests. Consumers of
> packages will often want to run these tests. Tools should be able to
> do this automatically. This proposal seeks to p
15 matches
Mail list logo
