Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 83038 invoked from network); 10 Nov 2009 16:31:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Nov 2009 16:31:11 -0000 Received: (qmail 92046 invoked by uid 500); 10 Nov 2009 16:31:11 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 92022 invoked by uid 500); 10 Nov 2009 16:31:11 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 92012 invoked by uid 99); 10 Nov 2009 16:31:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 16:31:11 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of feeder.of.the.bears@gmail.com designates 209.85.211.191 as permitted sender) Received: from [209.85.211.191] (HELO mail-yw0-f191.google.com) (209.85.211.191) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 16:31:08 +0000 Received: by ywh29 with SMTP id 29so166502ywh.32 for ; Tue, 10 Nov 2009 08:30:47 -0800 (PST) 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 :date:message-id:subject:from:to:content-type; bh=PGK3DGp90RBTqEtX3Yqm7K7CipUThOKzA1G/B59Ec/Q=; b=BM9s6DsyFvwf7eRt73f8IZizRQ/DdGIuJfGXQ7YWwIANCtH7r5S8K33xpW+8IWkipR hcCN3PSkvpZ3zxxYatQrZqD07ne5CkUDk5M8YYc4uLjDvY4y/RTxT1cu6cilAXlItsaB FxkXkXdT/OWykV+STmlhF5/9Zjyh2k3wQZxZk= 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=SNQlxoHskw+GJ39O5RaBnfXI8ZQfGYWCWv4RNvQyVthMVo96Ros/d8jeHsgX5h0tLE GZXy9MxxQKVstZlKoM78iZUB3hOJxugj3QWSGx9YiU87doQcFtxIpyGEXQfVfWrTsz9k Y6FISj4oN9qi6tWMEG5AvEm2K8MvG9Qg9VC0c= MIME-Version: 1.0 Received: by 10.91.159.22 with SMTP id l22mr566444ago.9.1257870646278; Tue, 10 Nov 2009 08:30:46 -0800 (PST) In-Reply-To: References: Date: Tue, 10 Nov 2009 08:30:46 -0800 Message-ID: Subject: Re: Test Cases From: David Pollak To: esme-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e641dc300b8fa0047806d52f --0016e641dc300b8fa0047806d52f Content-Type: text/plain; charset=UTF-8 On Tue, Nov 10, 2009 at 6:54 AM, Richard Hirsch wrote: > 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 > Your ticket is my command. > > Thanks. > > D. > > On Tue, Nov 10, 2009 at 3:19 PM, David Pollak > wrote: > > On Tue, Nov 10, 2009 at 12:17 AM, Richard Hirsch >wrote: > > > >> 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? Today's my ESME day (once I get the > > 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 > part > > of running the code in test mode so that it's (1) faster than selenium > but > > (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 > 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. > >> >> > >> > > >> > > > > > > > > -- > > 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 > > > -- 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 --0016e641dc300b8fa0047806d52f--