commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Knystautas" <>
Subject Re: Latka notes
Date Wed, 06 Mar 2002 02:54:55 GMT
I don't think I explained my idea 1 very well based on comments.

The issue I'm facing is making sure my latka suite stays current with the
site as developers maintain the site.  For an initial import, I might have a
webapp with 350 JSPs... I don't want to manually build the latka suite for
that.  More importantly, as the team of developers add more JSPs, I want to
know that some schmuck didn't add a JSP to CVS and not add it to the
functional test.

I would start with just a file system dir list, recursing through subdirs
and listing all *.jsp files.  (no link checking or wget or anything
complex... just pure dir.list() with recursion).  This would create a list
It would take these URLs and build the latka suite file.  If there already
was a latka suite file, it would append the files not already in there.
Really this is just a tool/script to maintain the latka suite file.

I was getting somewhat ahead of myself with the "meta" decription, but I was
thinking the filtering could get more advanced so that I included "*.jsp"
and "*.html", but excluded everything in "/include" since those pages are
not directly called.  Maybe I should just fashion this as an ant task so I
can leverage it's include/exclude file pattern capabilities.

On an unrelated note, I thought of two other validators... a) link checking,
and b) xml validation (if your servlet is supposed to output XML instead of
HTML).  Anyone else working on these kind of validators?

Serge Knystautas
Loki Technologies - Unstoppable Websites
----- Original Message -----
From: "Jeff Turner" <>
To: "Jakarta Commons Developers List" <>
Sent: Tuesday, March 05, 2002 5:34 PM
Subject: Re: Latka notes

> On Tue, Mar 05, 2002 at 01:42:17PM -0500, Serge Knystautas wrote:
> > I was just talking with a coworker about how to build some automated
> > for our webapp, and sure enough Latka does a lot of what I was thinking.
> > had a few other todo items I might contribute, assuming I can get my
> > to pay or can otherwise find the time.  I thought I'd bring up the ideas
> > first to get some feedback on whether this is going in a good or bad
> > direction:
> >
> > 1. meta process for test definition generation/maintenance
> > I'd like to define a "meta" XML file for a webapp that could declare
> > something like "all HTML pages and JSPs" in this webapp should be
> > Then new meta process code would use that meta XML to check that the
> > test definition meets these requirements... it would the recurse through
> > files in a webapp and look for them in the latka test file.
> How would you go about determining the URLs of "all HTML pages and
> JSPs"? Is this really *all* (ie you have inside information; it's your
> webapp you're testing), or just visible from the usual application
> workflow? Ie, is the list created by hand or created through a wget-like
> follow-the-links strategy?

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message