Last night at the Amsterdam Perl Mongers meeting, H. Merijn Brand gave a talk on the Perl Core Smoke Test Suite. This is a set of scripts which tries to run perl core tests on many different configurations and prepare a report of the results. The purpose of smoke testing is to identify problems in order to fix them before release. The more people that test the more information there will be about different platforms, configurations, etc.

The test suite was released on CPAN today, where it can be found under author id H/HM/HMBRAND as Test-Smoke-1.06.tgz.

Subscribing to smokers at perl.org is a good way to keep informed of "upgrades, malformed reports, warnings, expectations," and so on.

It's pretty easy to start smoking. You will need to create an empty directory where the perl source tree will be placed. Any files in that directory which are not part of the source tree will be removed when you run the test, so it is very important not to mix things up! On my system I just created a new user for the purpose and created a test subdirectory.

You will need to put the three scripts which are used somewhere, then edit the configuration as needed. The readme file contains specific information.

The smoke.sh script will run the test. If you set up a cronjob to run this daily this shouldn't take any more effort on your part than setiathome.

The test will do the following:

• refresh the perl source tree in the test directory using rsync;
• for many different configurations (the current set of testing configurations are limited by CPU power--Nicholas Clark has done 8x the number of the default):
  • configure,
  • make,
  • make test-prep, and
  • make test; and
• mail the results to smokers reports.

To run the tests you will need sufficient disk space to hold the perl source tree, a link fast enough to get source updates, and a computer that can handle lots of compiling. Also, you currently cannot use this test suite with windows, although that is being worked on.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.