From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v3 5/8] support/testing: add perl-libwww-perl test
Date: Sat, 24 Nov 2018 12:37:25 +0100 [thread overview]
Message-ID: <20181124123725.7c17ef1a@windsurf> (raw)
In-Reply-To: <CAB0FRstu85RTQ1tQm=fSkYOouLRZgxvkCq8VkXF+y0J82_o-xA@mail.gmail.com>
Hello,
On Sat, 24 Nov 2018 11:56:30 +0100, Fran?ois Perrad wrote:
> > Sorry if I haven't followed the previous discussion, but why do we have
> > this docstring ? Is it just for information ?
> >
> Yes, this is for information.
OK.
> By this way, we know that we don't need to write another test for HTTP-Date
> or IO-HTML.
This is not really true. Indeed, if you test HTTP-Date with plenty of
other packages installed, how are you sure that HTTP-Date has all the
necessary runtime dependencies it needs ?
Only a test with only HTTP-Date installed and its dependencies will
allow to verify this.
> > > + def test_run(self):
> > > + self.login()
> > > + self.module_test("LWP")
> > > + self.module_test("LWP::UserAgent")
> > > + self.module_test("LWP::Authen::Basic")
> > > + self.module_test("LWP::Authen::Digest")
> > > + self.module_test("HTTP::Message")
> > > + self.module_test("HTTP::Daemon")
> > > + self.module_test("WWW::RobotRules")
> >
> > Why are you testing specifically those modules ? What is the rule to
> > decide what modules are tested here ?
> >
> >
> libwww-perl is a special package/distribution from the beginning of the WWW
> history
> (started in 1995, see https://metacpan.org/changes/distribution/libwww-perl
> ).
> In fact, libwww-perl collection is a set of Perl modules.
> LWP (Lib World-Wide Web Perl) is just a name space for some of them, and
> doesn't match with the distribution name libwww.
> So, we need load most of them.
OK, so all those modules are the ones part of libwww-perl, i.e we are
not testing modules installed by other packages, correct ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-24 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 9:07 [Buildroot] [PATCH/next v3 0/8] suppport/testing: Perl interpreter and CPAN modules Francois Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 1/8] support/testing: add perl test Francois Perrad
2018-11-27 2:24 ` Ricardo Martincoski
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 2/8] scancpan: add generation of test Francois Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 3/8] support/testing: add perl-class-load test Francois Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 4/8] support/testing: add perl-gdgraph test Francois Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 5/8] support/testing: add perl-libwww-perl test Francois Perrad
2018-11-24 10:06 ` Thomas Petazzoni
2018-11-24 10:56 ` François Perrad
2018-11-24 11:37 ` Thomas Petazzoni [this message]
2018-11-24 13:42 ` François Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 6/8] support/testing: add perl-mail-dkim test Francois Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 7/8] support/testing: add perl-x10 test Francois Perrad
2018-11-24 9:07 ` [Buildroot] [PATCH/next v3 8/8] support/testing: add perl-xml-libxml test Francois Perrad
2018-12-03 19:53 ` [Buildroot] [PATCH/next v3 0/8] suppport/testing: Perl interpreter and CPAN modules Thomas Petazzoni
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=20181124123725.7c17ef1a@windsurf \
--to=thomas.petazzoni@bootlin.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