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;
        b=Fbi/399rH29FqHh3PIkoYLgut5gwGBGCx4/7m4GQDEZ+FeLUFYVYB+cpzJPQ3GBHdQ
         53egCEdi3TEEZNr29wH1vlNBqM+IKE4EmJ4atOzy8GP1XK/4EdlPBMuoNJnoyDuwxmTL
         4Kw4wWwx9f3UwXmX6fmXk8isv2Q1o/T1Ue6I0=
MIME-Version: 1.0
In-Reply-To: <c7fc82820911100011v4e7410f5wfbbc651a654a3940@mail.gmail.com>
References: <fa2d9f450911100002j583d3482ie702214303f43539@mail.gmail.com>
	 <c7fc82820911100011v4e7410f5wfbbc651a654a3940@mail.gmail.com>
Date: Tue, 10 Nov 2009 09:17:00 +0100
Message-ID: <fa2d9f450911100017h5bd2216cwec46d34d28240142@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

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.

D


On Tue, Nov 10, 2009 at 9:11 AM, Vassil Dichev <vdichev@apache.org> wrote:
> 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.com> 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 that
>> we can use.
>>
>> D.
>>
>