Hi Salve and others.
I have added an entry to http://adserver.szabgab.com/ advertising the
QA workshop.
It is in English and should show up in every country.
If you can send me texts in other languages as well with the
appropriate country code
I'd be glad to add them. See the linked yaml file to
A cautionary tale of why we must be very careful doing tests against
live systems.
http://thedailywtf.com/Articles/Ive-Got-The-Monkey-Now.aspx
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On 5 Feb 2008, at 14:44, Philippe Bruhat (BooK) wrote:
That's what I did at $work. I store all the results in a database, and
hope to come up with creative reports (especially historical ones) in
the future. TAP::Parser was very helpful in collecting the test
results.
Cool! Nice to hear of so
On Tue, Feb 05, 2008 at 09:58:39AM +0100, Thomas Klausner wrote:
>
> Therefore, my current approach would be to hack together a few scripts
> that fetch stuff from git, run the tests, collect the results, and
> report them.
That's what I did at $work. I store all the results in a database, and
On Feb 5, 2008, at 2:31 AM, "Gabor Szabo" <[EMAIL PROTECTED]> wrote:
On Feb 5, 2008 11:55 AM, Andy Armstrong <[EMAIL PROTECTED]> wrote:
You could look at buildbot. It can do all of the above. It's in
Python
if that matters :)
Or Tinderbox which was the original that buildbot copied.
A
On Feb 5, 2008 11:55 AM, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> You could look at buildbot. It can do all of the above. It's in Python
> if that matters :)
>
Or Tinderbox which was the original that buildbot copied. (Why did they have to
keep the GUI I don't know :)
Gabor
On 5 Feb 2008, at 08:58, Thomas Klausner wrote:
Are there any tools/frameworks available that would (in a perfect,
lazy
world) to the following:
* fetch various projects from git (HEAD, and some defined tags)
* run their test suite
* run Devel::Cover (eg via Build testcover)
* run some special
Thomas Klausner wrote:
> And I presume that the various CPAN smoking tools don't fit my needs,
> because they are designed to either smoke the whole of CPAN, or to send
> back test results after installing a given CPAN dist.
Remember that you can always bind your own local view of the CPAN with
C
Hi!
I've recently started a new job (and a small company (which btw explains
a certain CPANTS lagging on my part...)), and we want to smoke test our
code.
Are there any tools/frameworks available that would (in a perfect, lazy
world) to the following:
* fetch various projects from git (HEAD,
