[Buildroot] [RFC] testing: add python-cryptography tests

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Sep 6 08:06:56 UTC 2017


Hello,

On Tue, 05 Sep 2017 23:31:22 -0300, Ricardo Martincoski wrote:

> 1) I propose to merge this file into the existing test_python.py
> 
> The rationale is:
> For the long term:
> As I see, the test infra is used to detect regressions. It is important for both
> the basic features and also for the complex scenarios (like the dependencies of
> this package). But I don't expect to see tests added to every single package or
> python package (it would take a very long time to run all those tests), so this
> file probably will not grow too much and we can keep the tests together.

Actually, I am not sure I agree with this last part. I even think we
should probably have a minimal test for each and every Python package,
because the only way to verify that their dependencies are correct is
to have a runtime test for them. So it would be nice to have a very
simple way to write Python related tests, like a list of tuples
(Buildroot package, Python package to import or Python command to run),
and have the test infrastructure "generate" tests for all entries in
this list.

Yes, it's going to be a long test suite, with lots of tests, but the
test suite is anyway going to be long enough that it won't make sense
for anyone to run the full test suite. I really see two use cases for
the test suite:

 - You're doing tests in a specific area, and want to validate that
   you're not breaking things. For this use case, you'll just run the
   few test cases you're interested in.

 - We regularly run in a CI environment all the tests. For this
   situation, we don't really care how long it takes. Even if it takes
   24 hours to run the full test suite, I don't think it's a big
   problem.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com



More information about the buildroot mailing list