-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kevin F. Quinn wrote: > Well, it strikes me that most if not all of the organisational questions > are not relevant to a tester; the only technical question that is > relevant is 9 (keyword marking), and even that would be reworded for the > tester perspective. The main point being that a tester can be a willing > user, with no dev capabilities at all; the ebuild quiz is written for a > different target group. In fact, it's useful if testers are not developers, > as devs often make assumptions without realising it. > > I guess it comes down to what you want a tester to do. In my mind, the > task of a tester is to emerge the package normally, record the use flag > configuration, and exercise the application as much as possible. Possibly > repeating with other use flag configurations. If you want testers to do > ebuild QA, then the ebuild quiz becomes relevant, but I don't think it's > a good idea..
In my professional work, the pecking order is like this: developer --> integration/test --> system design --> management Of course, some of the developers I work with may disagree. ;) But the point is that the integration/test team knows about development; it just makes sense. The integration/test team needs to know a good deal about development *and* the overall system design to be affective. So I would say have all arch-testers take both the ebuild quiz and the newer QA/testing quiz. I suppose you could be more lax about scoring if you're really worried about not getting a large enough pool of testers. And I'm not arguing that an arch tester has to become a developer first; I'm just making the point that a good tester has the ability to switch back and forth between the 'big picture' and the 'bit level'. If you want fancy terminology, the testers need to know how to test the interfaces (in this case the portage API, probably by code walk throughs), and functional threads (you gave a great example, 'emerge the package normally, record the use flag configuration, and exercise the application'). Nathan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDHF2E2QTTR4CNEQARArbJAKCEZ7K6HiTFKpVy9mEVkaTU9TFUvQCeLlLE l8v1xMYUtLLa4cvF5meZyJo= =W6Sq -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
