On Wed, Jun 27, 2012 at 18:32 +0200, Ronny Pfannschmidt wrote:
> i noticed that there is no way to name items in those lists
could you insert this comment in context?
If you refer to the resourcefactory(multi=True) example, then
the name is known at factory-list construction time.
A a sidenote,
Hi Floris,
On Wed, Jun 27, 2012 at 16:59 +0100, Floris Bruynooghe wrote:
> Hello Holger,
>
> Thanks for the detailed document. As I understand it the vast
> majority of the functionality is already possible using funcargs.
> Maybe a summary of the benefits over plain funcargs could be helpful?
i noticed that there is no way to name items in those lists
On 06/27/2012 06:15 PM, holger krekel wrote:
> On Wed, Jun 27, 2012 at 08:43 -0600, Carl Meyer wrote:
>> I like it! In particular the parametrization support by passing a list
>> is a quite intuitive extension of the API.
>>
>> "atnode" s
On Wed, Jun 27, 2012 at 08:43 -0600, Carl Meyer wrote:
> I like it! In particular the parametrization support by passing a list
> is a quite intuitive extension of the API.
>
> "atnode" seems like an opaque arg name - what's wrong with "scope"? The
> latter name seems more intuitive to me. Would t
Hello Holger,
Thanks for the detailed document. As I understand it the vast
majority of the functionality is already possible using funcargs.
Maybe a summary of the benefits over plain funcargs could be helpful?
And some guidance for plugin writers on which of the two to choose
would also be help
Hi all,
based on on initial discussions with Ronny and Floris i have now written
a usage-level document for a new test resource management API. It aims
to better support plugin and test writers in managing cross-test-suite
resources such as databases, temporary directories, etc. It generalizes
t
