FAQ
I have a cron job that watches for changes to SVN, and when found the cron
script exports the code and runs the tests. The idea is to notify
developers if they check in code that causes testing to fail.

I'd like to move away from using my custom scripts to a more generic tool
that will do automated testing for all our packaged Perl code, not just the
Catalyst apps. (Since the Catalyst app is just another Perl distribution).
Perhaps something similar to what cpan testers use where email
notifications are sent but also provide a web-based history of testing.

Do you do anything similar? Anyone using Smolder and/or SmokeRunner::Multi
or other standard tools for their in-house code?

Thanks,

--
Bill Moseley
moseley@hank.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20100418/b94299fc/attachment.htm

Search Discussions

  • Dennis Daupert at Apr 18, 2010 at 8:44 pm

    On Sun, Apr 18, 2010 at 11:22 AM, Bill Moseley wrote:

    I have a cron job that watches for changes to SVN, and when found the cron
    script exports the code and runs the tests. The idea is to notify
    developers if they check in code that causes testing to fail.

    I'd like to move away from using my custom scripts to a more generic tool
    that will do automated testing for all our packaged Perl code, not just the
    Catalyst apps. (Since the Catalyst app is just another Perl distribution).
    Perhaps something similar to what cpan testers use where email
    notifications are sent but also provide a web-based history of testing.

    Do you do anything similar? Anyone using Smolder and/or SmokeRunner::Multi
    or other standard tools for their in-house code?

    Thanks,

    --
    Bill Moseley
    moseley@hank.org

    _______________________________________________
    List: Catalyst@lists.scsys.co.uk
    Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
    Searchable archive:
    http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
    Dev site: http://dev.catalyst.perl.org/

    Hi Bill,
    I'd suggest contacting Gabor Szabo (gabor@szabgab.com) He knows the
    territory, and has been involved with Perl's automated tests. He would be
    able to supply you with all the info you would need. I just noticed on his
    web site contact info page there's a note that he's teaching a master class
    at YAPC NA 2010: http://szabgab.com/contact.html

    /dennis
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20100418/08014531/attachment.htm
  • Tomas Doran at Apr 18, 2010 at 11:22 pm

    On 18 Apr 2010, at 16:22, Bill Moseley wrote:
    Do you do anything similar? Anyone using Smolder and/or
    SmokeRunner::Multi or other standard tools for their in-house code?
    At work, we're using hudson, and Tap::Harness::JUnit.

    It's entirely a dog and uses a million RAM, but does work quite well..

    There is also a simple Catalyst smoke test harness and viewer in the

    http://dev.catalyst.perl.org/repos/Catalyst/trunk/examples/SmokeServer/

    however, that became a bit limited/limiting for us, and I didn't have
    the time to keep extending / patching it.

    It is however entirely workable / useable given your code is in SVN.

    Cheers
    t0m
  • Kiffin Gish at Apr 19, 2010 at 7:44 am
    You might want to have a look at BuildBot, which is written in Python,
    but I've been using it for various Perl projects and find it very
    useful.
    On Sun, 2010-04-18 at 08:22 -0700, Bill Moseley wrote:
    I have a cron job that watches for changes to SVN, and when found the
    cron script exports the code and runs the tests. The idea is to
    notify developers if they check in code that causes testing to fail.

    I'd like to move away from using my custom scripts to a more generic
    tool that will do automated testing for all our packaged Perl code,
    not just the Catalyst apps. (Since the Catalyst app is just another
    Perl distribution). Perhaps something similar to what cpan testers
    use where email notifications are sent but also provide a web-based
    history of testing.


    Do you do anything similar? Anyone using Smolder and/or
    SmokeRunner::Multi or other standard tools for their in-house code?


    Thanks,

    --
    Bill Moseley
    moseley@hank.org

    _______________________________________________
    List: Catalyst@lists.scsys.co.uk
    Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
    Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
    Dev site: http://dev.catalyst.perl.org/

    --
    Kiffin Gish <kiffin.gish@planet.nl>
    Gouda, The Netherlands
  • Amiri Barksdale at Apr 20, 2010 at 12:49 am

    On Sun, Apr 18, 2010 at 08:22:56AM -0700, Bill Moseley wrote:
    I have a cron job that watches for changes to SVN, and when found the cron
    script exports the code and runs the tests. The idea is to notify
    developers if they check in code that causes testing to fail.

    I'd like to move away from using my custom scripts to a more generic tool
    that will do automated testing for all our packaged Perl code, not just the
    Catalyst apps. (Since the Catalyst app is just another Perl distribution).
    Perhaps something similar to what cpan testers use where email
    notifications are sent but also provide a web-based history of testing.

    Do you do anything similar? Anyone using Smolder and/or SmokeRunner::Multi
    or other standard tools for their in-house code?
    I can recommend Smolder--it's pretty nice. I have it hooked up to an svn
    commit hook so when people commit it uploads using smolder_smoke_signal.


    Amiri

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcatalyst @
categoriescatalyst, perl
postedApr 18, '10 at 3:22p
activeApr 20, '10 at 12:49a
posts5
users5
websitecatalystframework.org
irc#catalyst

People

Translate

site design / logo © 2022 Grokbase