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@intel.com] Sent: April 12, 2019 3:43 PM To: starlingx-discuss@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_a5URMMoWrJR4MbeA_UINnB... 2- https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEm... Regards, José