Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of hirsch.dick@gmail.com
 designates 209.85.218.210 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=RIInMspSRZMjBunBMGcV/RMpzG3kUGkN/4nhrTV/xIyYv4sa/y7Zd1p7jEszk/UFBB
         7fw2In3hXcFd7i32+b0f5Vf8rDSEKRxR0lVOMx9+/e5R+2QxCBL0EZ5pQu90OtetLs3l
         q9uiUSJWjgyro5aAp6h5EDQgGN9EXY8nGdY/8=
MIME-Version: 1.0
In-Reply-To: <cdbebedf0911100619k6905311dn726014057b1bc35c@mail.gmail.com>
References: <fa2d9f450911100002j583d3482ie702214303f43539@mail.gmail.com>
	 <c7fc82820911100011v4e7410f5wfbbc651a654a3940@mail.gmail.com>
	 <fa2d9f450911100017h5bd2216cwec46d34d28240142@mail.gmail.com>
	 <cdbebedf0911100619k6905311dn726014057b1bc35c@mail.gmail.com>
Date: Tue, 10 Nov 2009 15:54:53 +0100
Message-ID: <fa2d9f450911100654ldc11a3bm8f63c682294f4dcb@mail.gmail.com>
Subject: Re: Test Cases
From: Richard Hirsch <hirsch.dick@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

David: since today is your ESME day, could you look at Jira items
"ESME-105: Add password-related functionality" and "ESME-111: :OpenID
login/signon is broken" as well

Thanks.

D.

On Tue, Nov 10, 2009 at 3:19 PM, David Pollak
<feeder.of.the.bears@gmail.com> wrote:
> On Tue, Nov 10, 2009 at 12:17 AM, Richard Hirsch <hirsch.dick@gmail.com>w=
rote:
>
>> But the question is how to do perform the UI tests during the build
>> process. It is also possible for each developer to test the UI locally
>> before the commits but this is very inefficient.
>>
>
> Do you have a ticket open for this? =A0Today's my ESME day (once I get th=
e
> kids to school) and I would be interested in writing a few Lift testkit
> examples (folks on the Lift list have been asking for them). Specifically=
,
> testkit is (supposed) to be wired to certain hints that are emitted as pa=
rt
> of running the code in test mode so that it's (1) faster than selenium bu=
t
> (2) it still goes through the container (an instance of Jetty is started)=
 so
> that you're getting a full-stack test (well, except for the JavaScript,
> which requires the likes of selenium).
>
>
>>
>> D
>>
>>
>> On Tue, Nov 10, 2009 at 9:11 AM, Vassil Dichev <vdichev@apache.org> wrot=
e:
>> > Tests and documentation are definitely priority No.1 for me for the
>> > next couple of months.
>> >
>> > From my previous experience with Cactus the framework starts the
>> > container and connects to the test runner inside the container, which
>> > then has all the contexts it needs. We are already doing the same
>> > thing by running an embedded Jetty server, so I think we don't need
>> > it.
>> >
>> > Vassil
>> >
>> >
>> > On Tue, Nov 10, 2009 at 10:02 AM, Richard Hirsch <hirsch.dick@gmail.co=
m>
>> wrote:
>> >> Based on the fact that I made a build yesterday that led to a
>> >> non-functional app on stax, I started to think about tests in general
>> >> and the fact that we will soon need more tests to have some degree of
>> >> quality assurance.
>> >>
>> >> I've started a wiki page
>> >> (http://cwiki.apache.org/confluence/display/ESME/Tests) with test
>> >> cases.
>> >>
>> >> Ideally, we should have some sort of a test driver that tests the UI
>> >> as well during the build process. If I remember correctly, cactus has
>> >> something like this. I'll take a look and see if I find something tha=
t
>> >> we can use.
>> >>
>> >> D.
>> >>
>> >
>>
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Surf the harmonics
>