From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/5] support/testing: add package tests
Date: Sun, 5 Mar 2017 18:55:52 +0100 [thread overview]
Message-ID: <20170305185552.1729ee33@free-electrons.com> (raw)
In-Reply-To: <20170305162704.GJ3671@free.fr>
Hello,
On Sun, 5 Mar 2017 17:27:04 +0100, Yann E. MORIN wrote:
> > + def test_run(self):
> > + cpio_file = os.path.join(self.builddir, "images", "rootfs.cpio")
> > + self.emulator.boot(arch="armv5",
> > + kernel="builtin",
> > + options=["-initrd", cpio_file])
> > + self.emulator.login()
>
> I was wondering if the login phase could not be implicit. But then you
> may need to pass a pasword (like for the dropbear case).
>
> Yet, I still think that it should be implicit by default, unless you
> have to log in with a specific user/passwd...
Yes, we will definitely need some shortcuts for the common cases. But
that's clearly the kind of improvements that we can make gradually I
believe.
> > + cmd = "python --version 2>&1 | grep '^Python 2'"
> > + _, exit_code = self.emulator.run(cmd)
> > + self.assertEqual(exit_code, 0)
> > +
> > + cmd = "python -c 'import math; math.floor(12.3)'"
> > + _, exit_code = self.emulator.run(cmd)
> > + self.assertEqual(exit_code, 0)
> > +
> > + cmd = "python -c 'import ctypes;"
> > + cmd += "libc = ctypes.cdll.LoadLibrary(\"libc.so.1\");"
> > + cmd += "print libc.time(None)'"
> > + _, exit_code = self.emulator.run(cmd)
> > + self.assertEqual(exit_code, 0)
> > +
> > + cmd = "python -c 'import zlib'"
> > + _, exit_code = self.emulator.run(cmd)
> > + self.assertEqual(exit_code, 1)
>
> As I see it, there are a lot of similar constructs:
>
> cmd = "do-something"
> _, exit_code = self.emulator.run(cmd)
> self.assertEqual(exit_code, 0)
>
> Could we not aggregate the last two in a single command, like:
>
> cmd = "do-something"
> self.emulator.run.assert_exit(cmd, 0)
>
> Or something like that (use your imagination to come up with a
> meaningful function name...)
>
> We could then expand it with something like:
>
> self.emulator.run.assert_stdout(cmd, regexp)
>
> So that you could write:
>
> cmd = "python --version 2>&1"
> self.emulator.run.assert_stdout(cmd, "^Python 2")
Same comment here: yes, we will need some shortcuts.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-05 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 15:03 [Buildroot] [PATCH v2 0/5] Runtime testing infrastructure Thomas Petazzoni
2017-03-05 15:03 ` [Buildroot] [PATCH v2 1/5] support/testing: core " Thomas Petazzoni
2017-03-05 15:03 ` [Buildroot] [PATCH v2 2/5] support/testing: add core tests Thomas Petazzoni
2017-03-05 16:00 ` Yann E. MORIN
2017-03-05 17:54 ` Thomas Petazzoni
2017-03-05 15:03 ` [Buildroot] [PATCH v2 3/5] support/testing: add fs tests Thomas Petazzoni
2017-03-05 15:03 ` [Buildroot] [PATCH v2 4/5] support/testing: add package tests Thomas Petazzoni
2017-03-05 16:27 ` Yann E. MORIN
2017-03-05 17:55 ` Thomas Petazzoni [this message]
2017-03-05 15:03 ` [Buildroot] [PATCH v2 5/5] support/testing: add toolchain tests Thomas Petazzoni
2017-03-05 21:30 ` Ricardo Martincoski
2017-03-05 21:36 ` Thomas Petazzoni
2017-03-06 0:41 ` Ricardo Martincoski
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=20170305185552.1729ee33@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox