From: Francois Perrad <fperrad@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v2 0/8] suppport/testing: Perl interpreter and CPAN modules
Date: Fri, 23 Nov 2018 05:31:02 +0100 [thread overview]
Message-ID: <20181123043110.5353-1-francois.perrad@gadz.org> (raw)
test_perl.py allows to test the Perl interpreter and some of its core modules,
and it is used as base class for testing CPAN modules.
Now, scancpan could generate test for CPAN modules.
Currently, there are more than 100 CPAN modules, 25 of them are XS modules.
In order to limit the number of tests (and the execution time),
a test is generated only if the module have more than one direct dependencies
and have at least one XS dependencies.
V1 -> V2
- refactor with TestPerlBase class
- check "This is perl 5"
Francois Perrad (8):
support/testing: add perl test
scancpan: add generation of test
support/testing: add perl-class-load test
support/testing: add perl-gdgraph test
support/testing: add perl-libwww-perl test
support/testing: add perl-mail-dkim test
support/testing: add perl-x10 test
support/testing: add perl-xml-libxml test
.gitlab-ci.yml | 7 ++
support/testing/tests/package/test_perl.py | 66 ++++++++++++++++++
.../tests/package/test_perl_class_load.py | 28 ++++++++
.../tests/package/test_perl_gdgraph.py | 22 ++++++
.../tests/package/test_perl_libwww_perl.py | 41 ++++++++++++
.../tests/package/test_perl_mail_dkim.py | 28 ++++++++
.../testing/tests/package/test_perl_x10.py | 22 ++++++
.../tests/package/test_perl_xml_libxml.py | 22 ++++++
utils/scancpan | 67 +++++++++++++++++++
9 files changed, 303 insertions(+)
create mode 100644 support/testing/tests/package/test_perl.py
create mode 100644 support/testing/tests/package/test_perl_class_load.py
create mode 100644 support/testing/tests/package/test_perl_gdgraph.py
create mode 100644 support/testing/tests/package/test_perl_libwww_perl.py
create mode 100644 support/testing/tests/package/test_perl_mail_dkim.py
create mode 100644 support/testing/tests/package/test_perl_x10.py
create mode 100644 support/testing/tests/package/test_perl_xml_libxml.py
--
2.17.1
next reply other threads:[~2018-11-23 4:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 4:31 Francois Perrad [this message]
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 1/8] support/testing: add perl test Francois Perrad
2018-11-24 2:00 ` Ricardo Martincoski
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 2/8] scancpan: add generation of test Francois Perrad
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 3/8] support/testing: add perl-class-load test Francois Perrad
2018-11-24 2:01 ` Ricardo Martincoski
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 4/8] support/testing: add perl-gdgraph test Francois Perrad
2018-11-24 2:01 ` Ricardo Martincoski
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 5/8] support/testing: add perl-libwww-perl test Francois Perrad
2018-11-24 2:02 ` Ricardo Martincoski
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 6/8] support/testing: add perl-mail-dkim test Francois Perrad
2018-11-24 2:02 ` Ricardo Martincoski
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 7/8] support/testing: add perl-x10 test Francois Perrad
2018-11-24 2:02 ` Ricardo Martincoski
2018-11-23 4:31 ` [Buildroot] [PATCH/next v2 8/8] support/testing: add perl-xml-libxml test Francois Perrad
2018-11-24 2:03 ` 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=20181123043110.5353-1-francois.perrad@gadz.org \
--to=fperrad@gmail.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 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.