On Tue, Feb 14, 2017 at 1:02 PM, Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
Hi folks! I've got a question for everyone who helps out with
release
validation testing. It's related to the project to build a new system
for submitting those results. We have a ticket for designing that
system:
https://pagure.io/design/issue/483
and as part of the discussion there, we're wondering something. Given
that it's part of the new design that there's some kind of step where
you specify which particular image you're testing, does it make more
sense to you if you choose things in this order:
1. Pick a test to run
2. Pick an image to run the test on
Or this order:
1. Pick an image to test
2. Pick a test to run on the image
? It's pretty important to the design approach. Thanks!
I'm ambivalent on affecting the design because I don't know what the
consequence is, and I'm naturally contrary even with myself; HOWEVER
the way I have been working is image focused first, and test focused
second. That is, the image is the primary and static variable, and
then I go through various tests. If I'm regression testing, I'd do the
reverse where the test is what gets pinned, and I vary the image.
Being a bug magnet, I end up in way more regression tests than I want.
I'd say time wise I probably spend the same amount of time image
(version) pinned vs test pinned.
I think an Aeromax 2000 might be more useful than my little anecdote though.
--
Chris Murphy