From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] testing: add python-cryptography tests
Date: Wed, 6 Sep 2017 13:27:28 +0200 [thread overview]
Message-ID: <20170906132728.250c7caa@windsurf.lan> (raw)
In-Reply-To: <CAGm1_ktR=czPoLUdFpUnp4q2Ve_o=umgVgWOEkKnHdzkLyxvNQ@mail.gmail.com>
Hello,
On Wed, 6 Sep 2017 11:44:17 +0200, Yegor Yefremov wrote:
> > So I suppose the test you created is testing enough.
> > Could you (that knows more then me about the package) confirm it is OK to get
> > these messages?
> >
> > If you think testing for the output of the command is needed to determine
> > fail/pass, see TestNoTimezone. I didn't tested but I guess assertRegexpMatches
> > and assertNotRegexpMatches can be helpful.
>
> How can I perform tests for this testing framework locally?
You want to test the testing framework ? Seems weird.
Perhaps you just want to run the test cases ?
Quick start:
./support/testing/run-tests -l # to list the tests
./support/testing/run-tests -o /path/to/outputdir -k nameoftest # run a test case
> @Thomas do I see it right, that Python3 doesn't provide hashlib core
> property ans that this functionality is the by default compared to
> Python2?
Huh, I'm supposed to be able to answer this question ? :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-09-06 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 7:15 [Buildroot] [RFC] testing: add python-cryptography tests yegorslists at googlemail.com
2017-09-06 2:31 ` Ricardo Martincoski
2017-09-06 8:06 ` Thomas Petazzoni
2017-09-06 11:31 ` Ricardo Martincoski
2017-09-06 11:49 ` Thomas Petazzoni
2017-09-06 9:44 ` Yegor Yefremov
2017-09-06 11:09 ` Ricardo Martincoski
2017-09-06 11:27 ` Thomas Petazzoni [this message]
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=20170906132728.250c7caa@windsurf.lan \
--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