On Mon, 2016-12-05 at 10:33 +0100, Josef Skladanka wrote: > I kind of believe, that the "environment requirements" should be a part of > the > testplan - we should say that "testplan X needs testcase Y ran on Foo and > Bar" > in the testplan. Instead of listing all the different options in the > testcase, and then > just selecting "a version of it" in testplan.
Oh! Then yes, we absolutely agree. That's what I think too. In my head, a 'test case' - to this system - is some kind of resource locator for what's expected to be instructions on testing something, and an id. And that's all it is. Absolutely I agree we don't store any other metadata associated with the test case, but with the test plan. And yes, you were right in your assumption about what I meant by 'test environment'. One interesting thought I had, though - should we store the *test cases* in the middleware 'validate/report' thing I've been describing here, or should we store them in ResultsDB? The 'test plan' stuff should clearly go in the middleware, I think. But it's not so straightforward whether we keep the 'test cases' there or in ResultsDB, especially if they're just super-simple 'here's a URL and some identifiers for it' objects. Oh, BTW, I definitely was thinking that we should cope with test cases being moved around and having their human-friendly names changed, but still being recognized as 'the same test case'. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
