On Wed, Nov 30, 2016 at 6:29 PM, Adam Williamson <adamw...@fedoraproject.org > wrote:
> On Wed, 2016-11-30 at 18:20 +0100, Josef Skladanka wrote: > > I would try not to go the third way, because that is really prone to > erros > > IMO, and I'm not sure that "per context" is always right. So for me, the > > "TCMS" part of the data, should be: > > 1) testcases (with required fields/types of the fields in the "result > > response" > > 2) testplans - which testcases, possibly organized into groups. Maybe > even > > dependencies + saying "I need testcase X to pass, Y can be pass or warn, > Z > > can be whatever when A passes, for the testplan to pass" > > > > But this is fairly complex thing, to be honest, and it would be the first > > and only useable TCMS in the world (from my point of view). > > I have rather different opinions, actually...but I'm not working on > this right now and I'd rather have something concrete to discuss than > just opinions :) > > We should obviously set goals properly, before diving into implementation details :) I'm interested in what you have in mind, since I've been thinking about this particular kind of thing for the last few years, and it really depends on what you expect of the system.
_______________________________________________ qa-devel mailing list -- qa-de...@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
