All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Esquivel <benjamin.esquivel@linux.intel.com>
To: Jose Perez Carranza <jose.perez.carranza@intel.com>,
	poky@yoctoproject.org
Subject: Re: [PATCH] systemdboot: Add Test to check boot file is created correctly
Date: Mon, 29 Aug 2016 09:33:39 -0500	[thread overview]
Message-ID: <1472481219.5819.9.camel@linux.intel.com> (raw)
In-Reply-To: <1472247295-1155-1-git-send-email-jose.perez.carranza@intel.com>

Hello José, see my comments below.

On Fri, 2016-08-26 at 16:34 -0500, Jose Perez Carranza wrote:
>    Add Test case to verify Add test case to verify to Check
>    if EFI bootloaderfor systemd boot is correctly build
the two sentences above need revision, duplication and a space
missing.
>    inside of image.
> 
>  [YOCTO #9903]
> 
> Signed-off-by: Jose Perez Carranza <jose.perez.carranza@intel.com>
> ---
>  meta-yocto-bsp/lib/oeqa/selftest/systemd_boot.py | 51
> +++++++++++++++++++++---
>  1 file changed, 46 insertions(+), 5 deletions(-)
> 
> diff --git a/meta-yocto-bsp/lib/oeqa/selftest/systemd_boot.py b/meta-
> yocto-bsp/lib/oeqa/selftest/systemd_boot.py
> index f7f74db..7f57f66 100644
> --- a/meta-yocto-bsp/lib/oeqa/selftest/systemd_boot.py
> +++ b/meta-yocto-bsp/lib/oeqa/selftest/systemd_boot.py
> @@ -1,12 +1,11 @@
>  from oeqa.selftest.base import oeSelfTest
>  from oeqa.utils.commands import runCmd, bitbake, get_bb_var, runqemu
> -from oeqa.utils.decorators import testcase
> +from oeqa.utils.decorators import testcase, skipUnlessPassed
>  import re
>  import os
>  import sys
>  import logging
>  
> -
>  class Systemdboot(oeSelfTest):
>  
>      def _common_setup(self):
> @@ -27,12 +26,12 @@ class Systemdboot(oeSelfTest):
>          # Build a genericx86-64/efi gummiboot image
>          bitbake('mtools-native core-image-minimal')
>  
> -
>      @testcase(1445)
>      def test_efi_systemdboot_images_can_be_built(self):
>          """
>          Summary:     Check if systemd-boot images can be built
> correctly
> -        Expected:    1. File systemd-boot.efi should be available in
> $poky/build/tmp/deploy/images/genericx86-64
> +        Expected:    1. File systemd-boot.efi should be available
> in:
> +                         $poky/build/tmp/deploy/images/genericx86-64
>                       2. 'systemd-boot" can be built correctly
>          Product:     oe-core
>          Author:      Jose Perez Carranza <jose.perez.carranza@intel.
> com>
> @@ -41,7 +40,8 @@ class Systemdboot(oeSelfTest):
>  
>          # We'd use DEPLOY_DIR_IMAGE here, except that we need its
> value for
>          # MACHINE="genericx86-64 which is probably not the one
> configured
> -        systemdbootfile = os.path.join(get_bb_var('DEPLOY_DIR'),
> 'images', 'genericx86-64', 'systemd-bootx64.efi')
> +        systemdbootfile = os.path.join(get_bb_var('DEPLOY_DIR'),
> 'images', 'genericx86-64',
> +                                       'systemd-bootx64.efi')
>  
>          self._common_setup()
>  
> @@ -54,3 +54,44 @@ class Systemdboot(oeSelfTest):
>  
>          found = os.path.isfile(systemdbootfile)
>          self.assertTrue(found, 'Systemd-Boot file %s not found' %
> systemdbootfile)
> +
> +
> +    @testcase(1528)
> +    @skipUnlessPassed('test_efi_systemdboot_images_can_be_built')
> +    def test_efi_systemdboot_is_built_correctly(self):
Names as long as these impose some readability issues when listing the
tests. Please remind that the test name is composed by
module.class.function and if 'function' is this long then it leaves
little room for the rest of the fields in the full test name. It looks
like that level of description you're putting in the name is at the
first line of the docstring of the function. I suggest you pick a
function name short, unique and symbolic.
> +        """
> +        Summary:      Check if EFI bootloader for systemd is
> correctly build
> +        Dependencies: Image was built correctly on testcase 1445
> +        Steps:        1. Copy bootx64.efi file form the hddimg
> created
> +                         under build/tmp/deploy/images/genericx86-64
> +                      2. Check bootx64.efi was copied form hddimg
> +                      3. Verify the checksums from the copied and
> previously
> +                         created file are equal.
> +        Expected :    Systemd-bootx64.efi and bootx64.efi should be
> the same
> +                      hence checksums should be equal.
> +        Product:      oe-core
> +        Author:       Jose Perez Carranza <jose.perez.carranza@intel
> .com>
> +        AutomatedBy:  Jose Perez Carranza <jose.perez.carranza@intel
> .com>
> +        """
> +
> +        systemdbootfile = os.path.join(get_bb_var('DEPLOY_DIR'),
> 'images', 'genericx86-64',
> +                                       'systemd-bootx64.efi')
> +        systemdbootimage = os.path.join(get_bb_var('DEPLOY_DIR'),
> 'images', 'genericx86-64',
> +                                        'core-image-minimal-
> genericx86-64.hddimg')
> +        imagebootfile = os.path.join(get_bb_var('DEPLOY_DIR'),
> 'images', 'genericx86-64',
> +                                                'bootx64.efi')
> +        mcopynative =
> os.path.join(get_bb_var('STAGING_BINDIR_NATIVE'), 'mcopy')
> +
> +        #Step 1
> +        runCmd('%s -i %s ::EFI/BOOT/bootx64.efi %s' % (mcopynative
> ,systemdbootimage,
> +               imagebootfile))
> +
> +        #Step 2
> +        found = os.path.isfile(imagebootfile)
> +        self.assertTrue(found, 'bootx64.efi file %s was not copied
> from image'
> +                        % imagebootfile)
> +
> +        #Step 3
> +        result = runCmd('md5sum %s %s' % (systemdbootfile,
> imagebootfile))
> +        self.assertEqual(result.output.split()[0],
> result.output.split()[2],
> +                         '%s was not correclty generated' % 
typo at 'correctly'
> imagebootfile)
also, if you have an option to get the command output and print it,
would give the test runner more information.
> -- 
> 1.9.1
> 


  reply	other threads:[~2016-08-29 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 21:34 [PATCH] systemdboot: Add Test to check boot file is created correctly Jose Perez Carranza
2016-08-29 14:33 ` Benjamin Esquivel [this message]
2016-08-29 23:47   ` Jianxun Zhang
  -- strict thread matches above, loose matches on Subject: below --
2016-12-13 20:45 jose.perez.carranza

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1472481219.5819.9.camel@linux.intel.com \
    --to=benjamin.esquivel@linux.intel.com \
    --cc=jose.perez.carranza@intel.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.