- Original Message -
> From: "Tim Flink"
> To: qa-devel@lists.fedoraproject.org
> Sent: Thursday, March 6, 2014 3:29:32 PM
> Subject: Re: Default invocation of pytest for qadevel projects
>
> On Thu, 6 Mar 2014 05:44:15 -0500 (EST)
> Kamil Paral wrote:
&g
> Sure, I'm game for changing that. The two args that come to mind are:
>
> * --long (more generic than functional)
> * --func (short for functional)
>
> Any thoughts on which of those (if either) would be better?
I'd vote for --func, it retains the original meaning.
__
> Any thoughts on which of those (if either) would be better?
I do not really mind either, and do not have any strong preference. I'm used to
having the non-functional tests run by default, but I can easily manage any way
we decide to do it.
j.
___
qa
On Thu, 6 Mar 2014 05:44:15 -0500 (EST)
Kamil Paral wrote:
> > For the qadevel projects I'm aware of, we've been using pytest for
> > our unit/functional test runner.
> >
> > As part of the shared configuration, tests are split up into two
> > categories, unit and functional. Unit tests are fast
> For the qadevel projects I'm aware of, we've been using pytest for our
> unit/functional test runner.
>
> As part of the shared configuration, tests are split up into two
> categories, unit and functional. Unit tests are fast, do not touch the
> network, database or filesystem (there are some ex
For the qadevel projects I'm aware of, we've been using pytest for our
unit/functional test runner.
As part of the shared configuration, tests are split up into two
categories, unit and functional. Unit tests are fast, do not touch the
network, database or filesystem (there are some exceptions to
