Abner Silva <[email protected]> writes: > Hello, > > Sorry for my delay. I have been busy with other things. > > On Wed, 2012-10-17 at 13:47 +1300, Michael Hudson-Doyle wrote: >> We're going to be talking about test case management in LAVA at the >> Connect. I've brain-dumped some of my thoughts here: >> >> https://wiki.linaro.org/Platform/LAVA/Specs/TestCaseManagement >> >> Comments welcome. But if all you do is read it before coming to the >> session, that's enough for me :-) > > It's good to see people discussing it. I'm glad. > > Here are some comments about this initial spec: > > > [Terminologies] > > As a section says, it's not going to change the > test/testcase/testrun/testresult terminology for now. It would be good > to have each of these terminologies well explained somewhere. It might > be crystal clear to you guys, but for other people it might be confusing > when attending to the Linaro Connect session, since these same > terminologies are commonly used to represent other QA artifacts.
I've added something to the wiki page now: https://wiki.linaro.org/Platform/LAVA/Specs/TestCaseManagement#Assumptions Does that help? > [Test case concept] > > The first thing that passed through my head when I started thinking > about TC (sorry, I don't know what to call it considering LAVA naming) > inside LAVA, was that it would be a different Object/artifact/file, and > not really represented by the test definition concept/file LAVA already > have nowadays. > > Is that what you guys are planning to do? To consider the test def that > we have today as the TC entity? If yes, I probably have some questions > about it. The way I was thinking about it was to extend the test and test case models to be much richer (currently they're mostly just a normalization for the names of testruns and testresults). Cheers, mwh _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
