> 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
Perrin Harkins wrote:
> Back to your idea: you're obviously interested in the low-level
> optimization stuff, so of course you should go ahead with it. I don't
> think it needs to be a separate project, but improvements to the
> performance section of the guide are always a good idea.
It has
[EMAIL PROTECTED] wrote:
> ...
> Syntax error on line 51 of /etc/httpd/conf/vhosts/Vhosts.conf :
> "Invalid command 'PerlModule', perhaps mis-spelled or defined
> by a module not included in the server configuration"
>
> The directive was suggested by a Apache-Asp config
> information over its w
On Saturday 26 January 2002 03:40 pm, Sam Tregar wrote:
> Think search engines. Once you've figured out how to get your search
> database to fit in memory (or devised a cachin strategy to get the
> important parts there) you're essentially looking at a CPU-bound problem.
> These days the best sol
I have added lines bellow, in my Vhosts.conf file
NameVirtualHost 127.0.0.1
ServerName alliance
DocumentRoot /var/www/html/alliance
SetHandler perl-script
PerlModule Apache::ASP
PerlHandlerApache::ASP
PerlSetVar Global .
PerlSetVar StateDir /tmp
We have finally completed our initial public version of the DataBreeze
Web database system. It runs on Linux (or unix), Apache, Perl, ModPerl
and MySQL.
DataBreeze is written entirely in Perl and utilizes ModPerl within
Apache to speed performance. Feedback from the Perl/ModPerl/Apache
community
On Sat, 26 Jan 2002, Perrin Harkins wrote:
> > It all depends on what kind of application do you have. If you code is
> > CPU-bound these seemingly insignificant optimizations can have a very
> > significant influence on the overall service performance.
>
> Do such beasts really exist? I mean, I
On Sat, 26 Jan 2002, Perrin Harkins wrote:
>> It all depends on what kind of application do you have. If you code
>> is CPU-bound these seemingly insignificant optimizations can have a
>> very significant influence on the overall service performance.
>
> Do such beasts really exist? I mean, I gu
> It all depends on what kind of application do you have. If you code is
> CPU-bound these seemingly insignificant optimizations can have a very
> significant influence on the overall service performance.
Do such beasts really exist? I mean, I guess they must, but I've never
seen a mod_perl appl
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
14 matches
Mail list logo