From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/5] support/testing: add package tests
Date: Sun, 5 Mar 2017 17:27:04 +0100 [thread overview]
Message-ID: <20170305162704.GJ3671@free.fr> (raw)
In-Reply-To: <1488726201-6507-5-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2017-03-05 16:03 +0100, Thomas Petazzoni spake thusly:
> This commit adds some basic tests for two Buildroot packages: python and
> dropbear. These tests are by no mean meant to be exhaustive, but mainly
> to serve as initial examples for other tests.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> support/testing/tests/package/__init__.py | 0
> support/testing/tests/package/test_dropbear.py | 28 +++++++++++++++++++++
> support/testing/tests/package/test_python.py | 35 ++++++++++++++++++++++++++
> 3 files changed, 63 insertions(+)
> create mode 100644 support/testing/tests/package/__init__.py
> create mode 100644 support/testing/tests/package/test_dropbear.py
> create mode 100644 support/testing/tests/package/test_python.py
[--SNIP--]
> + # Would be useful to try to login through SSH here, through
> + # localhost:2222, though it is not easy to pass the ssh
> + # password on the command line.
> diff --git a/support/testing/tests/package/test_python.py b/support/testing/tests/package/test_python.py
> new file mode 100644
> index 0000000..5532fb5
> --- /dev/null
> +++ b/support/testing/tests/package/test_python.py
> @@ -0,0 +1,35 @@
> +import os
> +
> +import infra.basetest
> +
> +class TestPythonBase(infra.basetest.BRTest):
> + config = infra.basetest.BASIC_TOOLCHAIN_CONFIG + \
> +"""
> +BR2_PACKAGE_PYTHON=y
> +BR2_TARGET_ROOTFS_CPIO=y
> +# BR2_TARGET_ROOTFS_TAR is not set
> +"""
> +
> + 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...
> + 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")
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-03-05 16:27 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 [this message]
2017-03-05 17:55 ` Thomas Petazzoni
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=20170305162704.GJ3671@free.fr \
--to=yann.morin.1998@free.fr \
--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