For some background, I sent this email to Kamil yesterday with a diff
containing suggestions on splitting up the unit tests for CheckDetail
and python_utils. It didn't seem like a big deal to me at the time, so
I just sent it to him. Given the level and type of discussion that it
seems to be starte
On Wed, 5 Mar 2014 12:23:31 -0700
Tim Flink wrote:
> > That's true, but if we have zero-failed-test policy, why does it
> > matter? If you patch introduced a problem, you need to fix it, and
> > you might discover another one once you do. Yes, it might be a
> > sequence of steps rather than se
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
Fedora has been accepted as a mentoring org for GSoC 2014 and I'm
planning to sign up as a mentor again this year. I'm trying to think of
good projects that we could put on the list of suggestions of things
that we'd like students to work on and figured it was a good topic for
wider discussion.
I'
- Original Message -
> From: "Tim Flink"
> To: qa-devel@lists.fedoraproject.org
> Sent: Wednesday, March 5, 2014 8:23:31 PM
> Subject: Re: D19 Comments and Diff
>
> I'm generally of the mind that folks shouldn't have to dive into
> docstrings on tests in order to understand what is being
