Hi Mihail, Sorry for the delay in reviewing your test cases. They look good to me, but I have a couple of small comments (inline).
Thanks!! Belén On 04/12/2014 11:39, "Mihail, StanciuX" <[email protected]> wrote: >Hello everyone, > >I¹ve created the following TCs for the ³All layers² page in the new >managed mode under master. I would appreciate feedback on them: >https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1078 It might be an idea to add a step to test that, for layers with unsatisfied dependencies, only the checked layer dependencies are added to the project. So you can deselect a couple of dependencies from the dialog and check that they are not added to the project. >https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1073 At the very end of the "Action" section, the sentence "and the table shows all the tasks)." should say "and the table shows all the layers).". Just nitpicking really :) >https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1070 >https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1069 As part of 1069, I think we should also check that: * All table columns display and display in the right order * That the 'branch' for the layers with "Layer source" set to OpenEmbedded matches the branch of the release selected for the project (for example, if the project has release "Yocto Project master", the branch for the OpenEmbedded layers should say "master") * That only one instance of the core layers (openembedded-core, meta-yocto and meta-yocto-bsp) shows in this table, and that instance has a branch that matches the selected project release * That the "Dependencies" information links to the layer details pages * That the external links that appear next to the 'git repository url' and 'subdirectory' work Also, I am missing a test case for the filters (just discovered a bug in them: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7052). Can we create one? > >I would also appreciate some ideas on how I would go about testing the >³Showing imported layers that fail to clone² feature. (see design >document, page 15 for details >https://bugzilla.yoctoproject.org/show_bug.cgi?id=6590 ). This functionality is still not implemented, but once it is in place, you just need to import 3 layers: one with an invalid git url, one with a valid git url and a non-existent subdirectory, and one with a valid git url and a non-existing commit. Then build the layers: each layer should throw one type of cloning error. > >Regards, >Mihail > -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
