On Mon, Apr 17, 2023 at 2:44 PM Kamil Paral <kpa...@redhat.com> wrote:
> On Wed, Apr 12, 2023 at 5:57 AM Sumantro Mukherjee <sumuk...@redhat.com> > wrote: > >> There is a push from the >> Dekstop team to have toolbox as a default app in the installer iso as >> well. > > > The 'toolbox' package is already installed by default. Or do you mean some > related GUI app? > > >> ~~~~~~~~~~~~ >> Toolbox aka Toolbx should be usable. Toolbox should be able to list, >> create and provide the desired containerized environment to the user >> without root privileges. Toolbox images should be generally >> functional. >> >> Footnote - "What does this cover?": >> Toolbox's general functionality as covered by this test cases >> https://fedoraproject.org/wiki/QA:Testcase_toolbox >> ~~~~~~~~~~~~~ >> > > Already covered by Ben and Adam, so just a few additional notes: > * We can't block on toolbox *images*, unless they are marked as > release-blocking artifacts. If the Desktop team wants that, Ben will know > the right process to take. > * We can block on the toolbox cli command. We can say that it must list > existing containers, enter them, create a new one, etc. But since the > toolbox images are not release-blocking at the moment, they might be > broken, and then we won't be able to verify toolbox cli functionality > (that's probably not a showstopper to creating this criterion). It would > certainly make more sense to have both parts blocking, though :-) > * The criterion can't refer to the testcase for definitions. The criterion > must contain definitions, and the testcase is then written to test them, > that's the correct relation. > > _______________________________________________ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > Thanks for all the comments and advice!! I have rewritten this ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For any release-blocking deliverable whose default deployment includes toolbox, it must be possible to list existing containers, enter them, and create a new one. Footnote - "What does this cover?": Toolbox CLI should offer commands to be executed by the user which includes listing existing container images created by the toolbox, creating container images with the latest Fedora and RHEL and entering these containers. This criterion aims at blocking only the toolbox rpm functionality and not the OCI image which is supposed to be downloaded by user's choice. https://fedoraproject.org/wiki/QA:Testcase_toolbox ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
_______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
