Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 8077 invoked from network); 26 Mar 2010 17:08:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Mar 2010 17:08:14 -0000 Received: (qmail 67048 invoked by uid 500); 26 Mar 2010 17:08:14 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 67007 invoked by uid 500); 26 Mar 2010 17:08:13 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 67000 invoked by uid 99); 26 Mar 2010 17:08:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Mar 2010 17:08:13 +0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gerhard.petracek@gmail.com designates 209.85.220.228 as permitted sender) Received: from [209.85.220.228] (HELO mail-fx0-f228.google.com) (209.85.220.228) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Mar 2010 17:08:08 +0000 Received: by fxm28 with SMTP id 28so53031fxm.36 for ; Fri, 26 Mar 2010 10:07:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:content-type; bh=gg3Ggs2ujTSWK2+4q9/kZ8WQUwgqb6e5gyvwEJPy6jQ=; b=A2k/6OUK/qfqhMnQIjTizFoWd0a6aw+5/AOec89ggkdHr2YKAN5bFosWCPaVLVERV5 LORtZJ51Yw7iAKNBd6HK8MYvVgFzkOKsRCnfc8zUURgcCtV0RBSGerseQO3dOKrANbvp prGTybobkHKsplJ17Hfidsno019XkuVhn8j1A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=XUCmPj+BKJaMV044KE2wXScKyjHR1DodOSEUp/VSBmOomCA8nwtkPjzVODIP1u9xmf zktV6qb0bRc3qWF9nUE2CHmeFfMHapS9yaMLbonxB1f9PuDaUTzVtPs7MieVqrs9O3h5 nBF7tSkOgFwBJvnhBb6zaTwaHGqI5OnVOEJG8= MIME-Version: 1.0 Received: by 10.239.150.78 with HTTP; Fri, 26 Mar 2010 09:59:34 -0700 (PDT) In-Reply-To: References: <2332f63b1003260438i5f94998x6039e10ab133c05a@mail.gmail.com> <594431a91003260500q50383e46x1f2acb63381044ee@mail.gmail.com> <2332f63b1003260552w32eade8er5c03c18ecb0bfe33@mail.gmail.com> From: Gerhard Petracek Date: Fri, 26 Mar 2010 17:59:34 +0100 Received: by 10.239.165.9 with SMTP id v9mr108117hbd.152.1269623266260; Fri, 26 Mar 2010 10:07:46 -0700 (PDT) Message-ID: <2332f63b1003260959w4459ae7bvac15952606108aef@mail.gmail.com> Subject: Re: [GSoC] Proposal - Automated webapp tests To: MyFaces Development Content-Type: multipart/alternative; boundary=001485f794dec8b5610482b7333c --001485f794dec8b5610482b7333c Content-Type: text/plain; charset=ISO-8859-1 i just mention the most important issue (to keep it short): imo the current module is ~ok for basic myfaces-core tests. however, it doesn't fit e.g. for testing extensions. (the module uses too much mock implementations.) you won't see some important issues. so some tests aren't really reliable as soon as you are using it for testing something like extensions. imo it would be nice to have e.g. a jetty based test environment which we (and also our users) can use for testing extensions, (sample-) webapps, ... based on such an environment we can run unit tests (which shouldn't be as verbose as the current unit tests) with myfaces-core and also with mojarra. with the same environment we could also run jmeter- and something like httpunit-tests. the final solution should be a convenient test-suite with detailed and clear test-reports. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/3/26 Jakob Korherr > Frankly, I like MyFaces test. It "just" has to be improved, but we can > totally use it (actually that's what we're doing right now). The only thing > we can't use MyFaces test is for a real webapp-test, and that is were the > GSoC project comes up! > > Furthermore I don't think we need a subproject for this. Everything which > fits into automated testing fits into MyFaces test, so why not use the > existing one and improve it instead of creating yet another thing. > > Regards, > Jakob > > > 2010/3/26 Gerhard Petracek > > yes - it's an improved version of shale test. >> however, it would be nice to have a more modern solution e.g. with a >> fluent api, better reporting, ... >> so we could compare it with the existing solution. >> >> regards, >> gerhard >> >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >> >> 2010/3/26 Rudy De Busscher >> >> Isn't the Myfaces test (svn.apache.org/repos/asf/myfaces/test) not the >>> successor of shale test ? >>> >>> Automated test are indeed very useful, an alternative (easier to set up >>> maybe) of JSFUnit would be great. >>> Regards, >>> Rudy. >>> On 26 March 2010 12:38, Gerhard Petracek wrote: >>> >>>> hi jakob, >>>> >>>> additions: >>>> >>>> #1: yesterday (in our discussion about it) we also talked about a >>>> replacement for shale-test (e.g. based on easymock or mockito or ...). >>>> #2: since we also need it for sub-projects like extval, codi,... we >>>> should create e.g. a new extensions- or myfaces-commons-module for it. >>>> >>>> regards, >>>> gerhard >>>> >>>> >>>> http://www.irian.at >>>> >>>> Your JSF powerhouse - >>>> JSF Consulting, Development and >>>> Courses in English and German >>>> >>>> Professional Support for Apache MyFaces >>>> >>>> 2010/3/26 Jakob Korherr >>>> >>>> Hi, >>>>> >>>>> As we currently only have normal JUnit tests for automated testing in >>>>> MyFaces Core, it would be really great to have a way to test MyFaces Core >>>>> automatically in a real webapp at build time with maven. Of course, we >>>>> currently have the test-webapp, but we still have to check each page >>>>> manually here, if we want to test everything, which is long-winded. >>>>> >>>>> To accomplish something like that we could use test frameworks like >>>>> e.g. Canoo WebTest or HttpUnit + Jetty or something similar. I also want to >>>>> mention JSFUnit here, although we won't be able to use it since it is LGPL >>>>> licensed. >>>>> >>>>> The goal of this GSoC project would be to find alternatives and also to >>>>> find the best-fitting test framework for MyFaces Core. Then the goal would >>>>> be to integrate it with MyFaces Core, to define rules and provide how-tos >>>>> and to write a bunch of test cases. >>>>> >>>>> This would help us enormously in ensuring and improving the quality of >>>>> MyFaces Core by getting a far bigger test coverage and more possibilities to >>>>> test. >>>>> >>>>> What do you think? Are there any students who are interested in working >>>>> on this? >>>>> >>>>> Regards, >>>>> Jakob >>>>> >>>> >>>> >>> >> > --001485f794dec8b5610482b7333c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
i just mention the most important issue (to keep it short): imo the cu= rrent module is ~ok for basic myfaces-core tests.
however, it doe= sn't fit e.g. for testing extensions. (the module uses too much mock im= plementations.)
you won't see some important issues.=A0so some tests aren't re= ally reliable as soon as you are using it for testing something like extens= ions.

imo it would be nice to have e.g. a jetty ba= sed test environment which we (and also our users) can use for testing exte= nsions, (sample-) webapps, ...
based on such an environment we can run unit tests (which shouldn'= t be as verbose as the current unit tests) with myfaces-core and also with = mojarra.
with the same environment we could also run jmeter- and = something like=A0httpunit-tests.

the final solution should be a convenient test-suite wi= th detailed and clear test-reports.

regards,
=
gerhard

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in = English and German

Professional Support for Apache MyFaces

2010/3/26 Jakob Korherr &l= t;jakob.korher= r@gmail.com>
Frankly, I like MyFaces test. It "just" has to be improved, but w= e can totally use it (actually that's what we're doing right now). = The only thing we can't use MyFaces test is for a real webapp-test, and= that is were the GSoC project comes up!

Furthermore I don't think we need a subproject for this. Everything= which fits into automated testing fits into MyFaces test, so why not use t= he existing one and improve it instead of creating yet another thing.

Regards,
Jakob


2010/3/26 Gerha= rd Petracek <gerhard.petracek@gmail.com>
<= /div>

yes - it's an improved version of shale test.
however, it would be = nice to have a more modern solution e.g. with a fluent api, better reportin= g, ...
so we could compare it with the existing solution.

regards,
gerhard

http://www.irian.at
=
Your JSF powerhouse -
JSF Consulting, Development and
Courses in = English and German

Professional Support for Apache MyFaces


2010/3/26 Rudy De Busscher <r= debusscher@gmail.com>

Isn't the Myfaces test (svn.apache.org/repos/asf/myfaces/test)= not the successor of shale test ?
=A0
Automated test are indeed very useful,=A0an alternative (easier to set= up maybe) of JSFUnit would be great.
Regards,
Rudy.
On 26 March 2010 12:38, Gerhard Petracek <gerhard.petracek@gmail.com> wrote:
hi jakob,=20

additions:

#1:=A0yesterday (in our discussion about it) we also talked about a re= placement for shale-test (e.g. based on easymock or mockito or ...).
#2: since we also need it for sub-projects like extval, codi,... we sh= ould create e.g. a new extensions- or myfaces-commons-module for it.

regards,
gerhard=20


http://www.irian.at

Your JSF powerhouse -
JSF Consulting, = Development and
Courses in English and German

Professional Suppor= t for Apache MyFaces

2010/3/26 Jakob Korherr <jakob.korherr@gm= ail.com>=20

Hi,

As we curren= tly only have normal JUnit tests for automated testing in MyFaces Core, it = would be really great to have a way to test MyFaces Core automatically in a= real webapp at build time with maven. Of course, we currently have the tes= t-webapp, but we still have to check each page manually here, if we want to= test everything, which is long-winded.

To accomplish something like that we could use test frameworks like e.g= . Canoo WebTest or HttpUnit + Jetty or something similar. I also want to me= ntion JSFUnit here, although we won't be able to use it since it is LGP= L licensed.

The goal of this GSoC project would be to find alternatives and also to= find the best-fitting test framework for MyFaces Core. Then the goal would= be to integrate it with MyFaces Core, to define rules and provide how-tos = and to write a bunch of test cases.

This would help us enormously in ensuring and improving the quality of = MyFaces Core by getting a far bigger test coverage and more possibilities t= o test.

What do you think? Are there any students who are interested= in working on this?

Regards,
Jakob
=





--001485f794dec8b5610482b7333c--