All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Witt <randy.e.witt@linux.intel.com>
To: Daniel Istrate <daniel.alexandrux.istrate@intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oeqa/runtime: Added one runtime testcase in connman.
Date: Thu, 16 Jul 2015 10:46:59 -0700	[thread overview]
Message-ID: <55A7EE13.50203@linux.intel.com> (raw)
In-Reply-To: <1436970934-4635-1-git-send-email-daniel.alexandrux.istrate@intel.com>

Hi Daniel and Alex,


On 07/15/2015 07:35 AM, Daniel Istrate wrote:
> (testcase 223) Check that only one connmand runs in background.
>
> Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
> ---
>   meta/lib/oeqa/runtime/connman.py | 23 +++++++++++++++++++++++
>   1 file changed, 23 insertions(+)
>
> diff --git a/meta/lib/oeqa/runtime/connman.py b/meta/lib/oeqa/runtime/connman.py
> index cc537f7..b040400 100644
> --- a/meta/lib/oeqa/runtime/connman.py
> +++ b/meta/lib/oeqa/runtime/connman.py
> @@ -28,3 +28,26 @@ class ConnmanTest(oeRuntimeTest):
>           if status != 0:
>               print self.service_status("connman")
>               self.fail("No connmand process running")
> +
> +    @testcase(223)
> +    def test_only_one_connmand_in_background(self):
> +        """
> +        Summary:     Only one connmand in background
> +        Expected:    There will be only one connmand instance in background.
> +        Product:     BSPs
> +        Author:      Alexandru Georgescu <alexandru.c.georgescu@intel.com>
> +        AutomatedBy: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
> +        """
> +
> +        # Make sure that 'connmand' is running in background
> +        (status, output) = self.target.run(oeRuntimeTest.pscmd + ' | grep [c]onnmand')
> +        self.assertEqual(0, status, 'Failed to find "connmand" process running in background.')
> +
> +        # Start a new instance of 'connmand'
> +        (status, output) = self.target.run('connmand')
> +        self.assertEqual(0, status, 'Failed to start a new "connmand" process.')

If multiple instances of connmand can run, is that not a bug it connmand rather 
than in our configuration? I'm asking because it seems like this would be more 
suited as a connman test that would be part of ptest.

Otherwise, why not test all daemons for multiple instances?


  reply	other threads:[~2015-07-16 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 14:35 [PATCH] oeqa/runtime: Added one runtime testcase in connman Daniel Istrate
2015-07-16 17:46 ` Randy Witt [this message]
2015-07-16 19:47   ` Burton, Ross

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=55A7EE13.50203@linux.intel.com \
    --to=randy.e.witt@linux.intel.com \
    --cc=daniel.alexandrux.istrate@intel.com \
    --cc=openembedded-core@lists.openembedded.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.