You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Franklin, Matthew B." <mf...@mitre.org> on 2011/05/04 00:59:00 UTC
Javascript unit tests
I just added some Jasmine unit tests and the Jasmine maven plugin to
execute them headlessly (via HTMLUnit). I have heard good things about
this framework and having built a couple of tests, I find it very easy to
use.
The plugin produces jUnit style reports in the target/jasmine/ directory.
Can someone with administrator rights to the Jenkins build add that path
to the jUnit report plugin configuration so that they will show up on the
CI server?
-Matt
Re: Javascript unit tests
Posted by Marlon Pierce <mp...@cs.indiana.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry, never mind, I misunderstood Ate's email.
On 5/13/11 8:57 AM, Marlon Pierce wrote:
> It just worked for me on a clean svn checkout. Let me check Jenkins.
>
> On 5/13/11 8:53 AM, Ate Douma wrote:
>> On 05/04/2011 12:59 AM, Franklin, Matthew B. wrote:
>>> I just added some Jasmine unit tests and the Jasmine maven plugin to
>>> execute them headlessly (via HTMLUnit). I have heard good things about
>>> this framework and having built a couple of tests, I find it very easy to
>>> use.
>>>
>>> The plugin produces jUnit style reports in the target/jasmine/ directory.
>>> Can someone with administrator rights to the Jenkins build add that path
>>> to the jUnit report plugin configuration so that they will show up on the
>>> CI server?
>
>> I just tried and ran the build, but it failed :(
>> See error report on rave-commits@ #37
>
>> Seems like configuring this isn't trivial, or at least not something I understand how to do.
>
>> I simply followed the instructions from [1] as much as possible, but its possibly no exact match (anymore) for the current Jenkins setup.
>
>> I added a post-build action for "Publish testing tools result report", configured a "Custom Tool" as there isn't a "Jasmin Tool" preconfigured and specified file include pattern: "**/jasmine/TEST*.xml".
>> It also (and only) allows to configure a "custom stylesheet", so maybe something is needed there?
>
>> For the time being I'll remove this post-build action again.
>
>> Ate
>
>> [1] https://github.com/searls/jasmine-maven-plugin#readme
>
>>>
>>> -Matt
>>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNzSu+AAoJEEfVXEODPFIDzFIH/0wLEPrSLeU0N3qpoYbgwJSe
bRykFjJSWE+f06gC9lWTiA9Yi0NkFjK4z0h1CjNzLWOq7sGfysE5uxds+QC1vov2
QFMEKMAcg2PAH6hwcWdKwFQQcsK57fGQwjkWHZ/VwvTP9h3FRhx6nr9AW2BsEtRO
LEqGDNRXRSl4QTv9h56gW551EJJXgvlySfLqvfIaQ1KKBYcnW5FLzK1gi4hNvtAS
/LHtBXumiREQI3JXMbMHC7VlAMqGqNBTsGJQTM1fQsAOEVX42lQIhWhz+dn3zGdY
lro44QNfk8L7LGec8iQPLV12p24SY5uVxSOKPFkJkpQ9LYFRfTKJ7nlRUX9YGaI=
=45YP
-----END PGP SIGNATURE-----
Re: Javascript unit tests
Posted by Marlon Pierce <mp...@cs.indiana.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It just worked for me on a clean svn checkout. Let me check Jenkins.
On 5/13/11 8:53 AM, Ate Douma wrote:
> On 05/04/2011 12:59 AM, Franklin, Matthew B. wrote:
>> I just added some Jasmine unit tests and the Jasmine maven plugin to
>> execute them headlessly (via HTMLUnit). I have heard good things about
>> this framework and having built a couple of tests, I find it very easy to
>> use.
>>
>> The plugin produces jUnit style reports in the target/jasmine/ directory.
>> Can someone with administrator rights to the Jenkins build add that path
>> to the jUnit report plugin configuration so that they will show up on the
>> CI server?
>
> I just tried and ran the build, but it failed :(
> See error report on rave-commits@ #37
>
> Seems like configuring this isn't trivial, or at least not something I understand how to do.
>
> I simply followed the instructions from [1] as much as possible, but its possibly no exact match (anymore) for the current Jenkins setup.
>
> I added a post-build action for "Publish testing tools result report", configured a "Custom Tool" as there isn't a "Jasmin Tool" preconfigured and specified file include pattern: "**/jasmine/TEST*.xml".
> It also (and only) allows to configure a "custom stylesheet", so maybe something is needed there?
>
> For the time being I'll remove this post-build action again.
>
> Ate
>
> [1] https://github.com/searls/jasmine-maven-plugin#readme
>
>>
>> -Matt
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNzSq6AAoJEEfVXEODPFID7HkH/1b994sLsYKwanM0EMEZ/gG9
M2/aq7PiHWZGDABTUJDY7SuHC4LHWPsZMVJVTtqNp4N4GMKScSXA+i//Mugns8j/
w6W2YVQZNvlnfEE2vsCdPvREW9hvb+KMthtaxsH+VZFsUbnggLbVsdqkJOTk2atA
9UN0EiYM8wqUHIE7+JH7QCmval5EET9/5BNphU9vFVQLEsbPGZ5RXB1THVjDnjUq
JDg2MWziJGSltos/QVfxP3O88Rax1SCn9Pm0kgwZ5XtkhgPbhffPOOepDrmFcJBF
frKs2A2P4vdJcMyY9UQRooWKRUROrhuQ9NqBR7E+UtinAMFT68RKsdRLaOpwNxk=
=jLG2
-----END PGP SIGNATURE-----
Re: Javascript unit tests
Posted by Ate Douma <at...@douma.nu>.
On 05/16/2011 07:05 PM, Franklin, Matthew B. wrote:
> Can you grant me permissions to configure the build? I have a lot of
> Hudson/Jenkins configuration experience...
No, I can't.
Formally this is something you should request yourself from your PMC Chair
(Incubator in this case), see also: http://wiki.apache.org/general/Hudson
But for this case, I happened to ask Upayavira, who already got it "done" for you :)
Thanks Upayavira!
This means you should have received an email with your new Hudson account
credentials!
Rock it :)
Ate
>
> On 5/13/11 8:53 AM, "Ate Douma"<at...@douma.nu> wrote:
>
>> On 05/04/2011 12:59 AM, Franklin, Matthew B. wrote:
>>> I just added some Jasmine unit tests and the Jasmine maven plugin to
>>> execute them headlessly (via HTMLUnit). I have heard good things about
>>> this framework and having built a couple of tests, I find it very easy
>>> to
>>> use.
>>>
>>> The plugin produces jUnit style reports in the target/jasmine/
>>> directory.
>>> Can someone with administrator rights to the Jenkins build add that path
>>> to the jUnit report plugin configuration so that they will show up on
>>> the
>>> CI server?
>>
>> I just tried and ran the build, but it failed :(
>> See error report on rave-commits@ #37
>>
>> Seems like configuring this isn't trivial, or at least not something I
>> understand how to do.
>>
>> I simply followed the instructions from [1] as much as possible, but its
>> possibly no exact match (anymore) for the current Jenkins setup.
>>
>> I added a post-build action for "Publish testing tools result report",
>> configured a "Custom Tool" as there isn't a "Jasmin Tool" preconfigured
>> and
>> specified file include pattern: "**/jasmine/TEST*.xml".
>> It also (and only) allows to configure a "custom stylesheet", so maybe
>> something
>> is needed there?
>>
>> For the time being I'll remove this post-build action again.
>>
>> Ate
>>
>> [1] https://github.com/searls/jasmine-maven-plugin#readme
>>
>>>
>>> -Matt
>>>
>>
>
Re: Javascript unit tests
Posted by "Franklin, Matthew B." <mf...@mitre.org>.
Can you grant me permissions to configure the build? I have a lot of
Hudson/Jenkins configuration experience...
On 5/13/11 8:53 AM, "Ate Douma" <at...@douma.nu> wrote:
>On 05/04/2011 12:59 AM, Franklin, Matthew B. wrote:
>> I just added some Jasmine unit tests and the Jasmine maven plugin to
>> execute them headlessly (via HTMLUnit). I have heard good things about
>> this framework and having built a couple of tests, I find it very easy
>>to
>> use.
>>
>> The plugin produces jUnit style reports in the target/jasmine/
>>directory.
>> Can someone with administrator rights to the Jenkins build add that path
>> to the jUnit report plugin configuration so that they will show up on
>>the
>> CI server?
>
>I just tried and ran the build, but it failed :(
>See error report on rave-commits@ #37
>
>Seems like configuring this isn't trivial, or at least not something I
>understand how to do.
>
>I simply followed the instructions from [1] as much as possible, but its
>possibly no exact match (anymore) for the current Jenkins setup.
>
>I added a post-build action for "Publish testing tools result report",
>configured a "Custom Tool" as there isn't a "Jasmin Tool" preconfigured
>and
>specified file include pattern: "**/jasmine/TEST*.xml".
>It also (and only) allows to configure a "custom stylesheet", so maybe
>something
>is needed there?
>
>For the time being I'll remove this post-build action again.
>
>Ate
>
>[1] https://github.com/searls/jasmine-maven-plugin#readme
>
>>
>> -Matt
>>
>
Re: Javascript unit tests
Posted by Ate Douma <at...@douma.nu>.
On 05/04/2011 12:59 AM, Franklin, Matthew B. wrote:
> I just added some Jasmine unit tests and the Jasmine maven plugin to
> execute them headlessly (via HTMLUnit). I have heard good things about
> this framework and having built a couple of tests, I find it very easy to
> use.
>
> The plugin produces jUnit style reports in the target/jasmine/ directory.
> Can someone with administrator rights to the Jenkins build add that path
> to the jUnit report plugin configuration so that they will show up on the
> CI server?
I just tried and ran the build, but it failed :(
See error report on rave-commits@ #37
Seems like configuring this isn't trivial, or at least not something I
understand how to do.
I simply followed the instructions from [1] as much as possible, but its
possibly no exact match (anymore) for the current Jenkins setup.
I added a post-build action for "Publish testing tools result report",
configured a "Custom Tool" as there isn't a "Jasmin Tool" preconfigured and
specified file include pattern: "**/jasmine/TEST*.xml".
It also (and only) allows to configure a "custom stylesheet", so maybe something
is needed there?
For the time being I'll remove this post-build action again.
Ate
[1] https://github.com/searls/jasmine-maven-plugin#readme
>
> -Matt
>