2015-10-26 23:24 GMT+01:00 Jérémy Lal <kapo...@melix.org>:

>
>
> 2015-10-26 23:22 GMT+01:00 dann frazier <da...@dannf.org>:
>
>> On Fri, Oct 23, 2015 at 09:14:54AM +0200, Jérémy Lal wrote:
>> > 2015-10-23 2:32 GMT+02:00 dann frazier <da...@debian.org>:
>> >
>> > > Source: nodejs
>> > > Version: 4.0.0~dfsg-2
>> > > Severity: wishlist
>> > > Tags: patch
>> > >
>> > > Attached is a patch to add a couple simple autopkgtests to nodejs.
>> > >
>> >
>> > Hello,
>> > beside a very simple test like
>> > nodejs -e "console.log('test');"
>>
>> The attached patch should do that.
>>
>> > i don't see the point of testing further since hundreds of tests are
>> > already run
>> > during package build.
>>
>> I could also wrap those tests up to run against the host binary - is
>> that something you'd be interested in including?
>>
>> fyi, my goal is to be able to run tests against an existing binary
>> package to make sure there are no issues due to an ancillary software
>> update (e.g. kernel).
>>
>>
> Don't bother. It is true that autopkgtests have different use cases than
> tests done
> during build. I'll apply your patch as is.
>


Ha, spoke too fast (there should be an acronym for that).

Maybe pure upstream js tests could be part of autopkgtests, because they
just
require source package with patches applied + nodejs runtime.
The only (solvable) problem is to pass correct cpu param to the test suite.
That would separate building from testing, which is often a problem on
buildd
servers where slowdowns can make some tests timeout. Maybe also more
control over autopkgtest environment could enable more tests (ipv6, tty).

I'll look into it before next upstream release.

Jérémy
_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to