Smoke testing

[Rob Kinyon]

All -

Steve Little (stevan) and I are planning to build some sort of
Test.Harness subclass that will do automated testing, collecting
results server-side. Doing things this way will allow for one
smoke-testing server to handle multiple browsers. All that would need
is the browser to open one page and it would then go ahead and run all
the tests suites we want it to smoke, 302'ing as it reports back. (The
reporting back would be the meat of the subclass.)

We won't have time to build it until early next week. Any thoughts?

Rob

[Casey West]

On Jul 8, 2005, at 11:11 PM, Rob Kinyon wrote:

> We won't have time to build it until early next week. Any
> thoughts?

From the Open JSAN side of things, I'd love to have these tests send
email
to this list. Would it be okay with you if I created a Perl Module
that you
could use directly to send those messages? I'll document it we can work
out the specifics together. Sound good? This is something that can
happen
before you begin Real Work on your Smoke Testing system.

--
Casey West

[Rob Kinyon]

Casey -

Sounds like fun. Steve and I talked and we're looking to have
something basic working Monday morning. Nothing productionized, just
proof-of-concept. We can add stuff to it as we see fit.

Unless people have an objection, I plan on using Catalyst for the
serverside code.

Rob

[Casey West]

On Jul 9, 2005, at 4:36 PM, Rob Kinyon wrote:

>
> Casey -
>
> Sounds like fun. Steve and I talked and we're looking to have
> something basic working Monday morning. Nothing productionized, just
> proof-of-concept. We can add stuff to it as we see fit.
>

Can't wait.

> Unless people have an objection, I plan on using Catalyst for the
> serverside code.
>

Whatever works is great by me. Though I'm curious if you could define
what "server side" does. :-)


--
Casey West

[David Wheeler]

On Jul 9, 2005, at 1:36 PM, Rob Kinyon wrote:

> Sounds like fun. Steve and I talked and we're looking to have
> something basic working Monday morning. Nothing productionized, just
> proof-of-concept. We can add stuff to it as we see fit.

Something to keep in mind: I plan to add support for pure .js files
for the test files in the near future, so they wouldn't have to have
all of the HTML scaffolding around them, and they'd be easier to test
in other applications (e.g., Director). Not sure if that will affect
your work, but it's something to keep in mind.

Best,

David