[Starlingx-discuss] [Containers] Test Scenarios based on feature plan

[Wensley, Barton]

José,

In that case, please try to look at the full set of commits for a storyboard before writing the testcases - that way you will have the big picture and can avoid writing testcases that have been invalidated by a later commit.

Bart
-----Original Message-----
From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] 
Sent: April 15, 2019 3:56 PM
To: Wensley, Barton; starlingx-discuss at lists.starlingx.io
Cc: Miller, Frank
Subject: RE: [Containers] Test Scenarios based on feature plan

Hi Bart 

Also regarding for your feedback, for some storyboard the description is quite generic and with this sometimes is hard to visualize the test scenarios, that is why we are checking directly the patches to try to get more specific information, did you know if there is another place where this is documented? A wiki or a spec document where we can take as a base for our scenarios proposal? 

Regards,
José


> -----Original Message-----
> From: Perez Carranza, Jose
> Sent: Monday, April 15, 2019 1:49 PM
> To: 'Wensley, Barton' <Barton.Wensley at windriver.com>; starlingx-
> discuss at lists.starlingx.io
> Cc: Miller, Frank <Frank.Miller at windriver.com>
> Subject: RE: [Containers] Test Scenarios based on feature plan
> 
> Hi Bart
> 
> Thanks for your feedback, sure I'll base the scenarios more on the on the
> storyboard specification rather than the feature commits.
> 
> Regards,
> José
> 
> 
> > -----Original Message-----
> > From: Wensley, Barton [mailto:Barton.Wensley at windriver.com]
> > Sent: Monday, April 15, 2019 1:21 PM
> > To: Perez Carranza, Jose <jose.perez.carranza at intel.com>; starlingx-
> > discuss at lists.starlingx.io
> > Cc: Miller, Frank <Frank.Miller at windriver.com>
> > Subject: RE: [Containers] Test Scenarios based on feature plan
> >
> > José,
> >
> > One general comment I have is that your testcases seem to be based on
> > specific commits (at least that is what appears in the references
> > column). I'd prefer to see your testcases based on what is captured in
> > the specs and the storyboards. The problem with defining testcases at
> > the commit level is that there are often several intermediate commits
> > required to complete a piece of functionality. If you are creating a
> > testcase based on a particular commit message, it is very possible
> > that the behavior was changed in subsequent commits and your testcase
> > won't be right. Instead, basing your testcases on the behavior
> > described in the spec or the storyboard should give a better view of what the
> final system behavior is supposed to be.
> >
> > Bart
> >
> > -----Original Message-----
> > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com]
> > Sent: April 12, 2019 3:43 PM
> > To: starlingx-discuss at lists.starlingx.io
> > Cc: Miller, Frank; Wensley, Barton
> > Subject: [Containers] Test Scenarios based on feature plan
> >
> > Hi All
> >
> > We are working on the analysis of the storyboards  already merged on
> > feature plan [1] to create test cases, we kindly ask for your feedback
> > on this development so we can create more accurate tests for the
> > different functionalities, you can find our continuous contribution on a
> google sheet [2].
> > Some scenarios have only general description whilst other have been
> > completed with Test Steps.
> >
> > 1 -
> >
> https://docs.google.com/spreadsheets/d/1lMMclUmLMPTuk_a5URMMoWrJR4
> > MbeA_UINnBliumg2Y/edit#gid=991138079
> > 2-
> >
> https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0Bs
> > MHohhEmhwpauDo/edit#gid=637180508
> >
> >
> > Regards,
> > José
> >