David Wheeler sent the following bits through the ether:
> we can't really figure out a way to automate the testing of the UI
Well, on our current project we're using using OpenFrame[1] and the
Template Toolkit to completely seperate application logic from
presentation logic. We have application
> Have you considered talking about Testing at OSC this summer? Mischael
> Schwern's talk was a great success last summer.
Thanks for the suggestion. I'll think about it, and see what I can
do.
> Also writing things down as a doc explaining how things work, with some
> light examples, to add
Rob Nagler wrote:
> FWIW, we are very happy with our unit test structure. It has evolved
> over many years, and many different languages. I've appended a simple
> example, because it is quite different than most of the unit testing
> frameworks out there. It uses the XP philosophy of once and
Gunther Birznieks writes:
> From the description of your scenario, it sounds like you have a long
> product life cycle etc.
We release weekly. We release to test multiple times a day. We "code
freeze" the test system over the weekend.
We run all weekly jobs on test during the day on Sat, and
Perrin Harkins writes:
> But what about the actual data? In order to test my $product->name()
> method, I need to know what the product name is in the database. That's
> the hard part: writing the big test data script to run every time you
> want to run a test (and probably losing whatever data
Hi Craig,
> Have you ever heard of the hw verification tool Specman Elite by Verisity
> (www.verisity.com)?
No, but it looks interesting. It would be good to have something like
this for unit tests. I haven't had very good experience with
automated acceptance testing, however. The software s
From the description of your scenario, it sounds like you have a long
product life cycle etc.
I think your testing, especially regression testing and the amount of
effort you put into it makes a lot of sense because your software is a
long-term investment possibly even a product.
I think you
On Sat, 26 Jan 2002 00:23:40 -0500
"Perrin Harkins" <[EMAIL PROTECTED]> wrote:
> But what about the actual data? In order to test my $product->name()
> method, I need to know what the product name is in the database. That's
> the hard part: writing the big test data script to run every time you
David Wheeler wrote:
> Hi All,
>
> A big debate is raging on the Bricolage development list WRT CVS
> configuration and application testing.
>
>
>http://www.geocrawler.com/mail/thread.php3?subject=%5BBricolage-Devel%5D+More+on+Releases&list=15308
>
> It leads me to a question about testing. B
> Gunther Birznieks writes:
> > the database to perform a test suite, this can get time consuming
and
> > entails a lot of infrastructural overhead.
>
> We haven't found this to be the case. All our database operations are
> programmed. We install the database software with an RPM, run a
> progr
On Sat, 26 Jan 2002, Gunther Birznieks wrote:
> I agree that testing is great, but I think it is quite hard in practice.
> Also, I don't think programmers are good to be the main people to write
> their own tests. It is "OK" for programmers to write their own tests but
> frequently it is the u
Gunther Birznieks writes:
> the database to perform a test suite, this can get time consuming and
> entails a lot of infrastructural overhead.
We haven't found this to be the case. All our database operations are
programmed. We install the database software with an RPM, run a
program to build
I suppose it depends on what you want out of testing.
Frequently, unit testing is OK in simple applications. But in an
application whose job it is to communicate with a mainframe or back-end
databases, frequently the tests you might perform are based on some
previous persistent state of the da
> Have you tried webchat? You can find webchatpp on CPAN.
Just had a look. It appears to be a rehash of chat (expect) for the
web. Great stuff, which is really needed and demonstrates the power
of Perl for test scripting.
But...
This is a bit hard to explain. There are two types of XP testi
On Fri, 2002-01-25 at 10:12, Perrin Harkins wrote:
> Have you tried webchat? You can find webchatpp on CPAN.
Looks interesting, although the documentation is rather sparse. Anyone
know of more examples than come with it?
Thanks,
David
--
David Wheeler AIM
> There are many web testers out there. To put it bluntly, they don't
> let you write maintainable test suites. The key to maintainability is
> being able to define your own domain specific language.
Have you tried webchat? You can find webchatpp on CPAN.
> Is anyone familiar with how to go about setting up a test suite for a
> web UI -- without spending an arm and a leg? (Remember, Bricolage is an
> OSS effort!).
Yes, it's very easy. We did this using student labor, because it is
an excellent project for students and it's probably cheaper. It's
17 matches
Mail list logo
