Hi Mateusz,
Yes, I would run the Perl scripts from a "execute shell" step. However,
I would recommend separating the software build and the running of the
tests into two separate jobs. If the build job does not succeed for some
reason, there is no need to run the tests, and this will give you a more
detailed view of the software status. That is, you'll know (for example)
that it compiles but has test failures.
For summarizing the test results, it will be easiest if you can get the
results in XUnit format, e.g. by using a JUnit-like test framework. Here
are links to several. With the output in XUnit format you can use
plugins to visualize and track the test results.
http://stackoverflow.com/questions/502644/how-can-i-do-unit-testing-in-perl
http://stackoverflow.com/questions/1369108/is-there-a-junit-for-perl
http://damien.krotkine.com/2009/11/25/perl-tests-in-hudson-via-junit.html
http://www.perlmonks.org/?node_id=537441
-Eric
On 8/21/2013 5:01 AM, pm wrote:
Hi,
I'm a trainee at a testers team, which is going to use Jenkins to do
automated testing of the products of our company. The tests are written in
Perl. Is it a good practice to run these by executing shell as a post-build
action? Or are there any plugins which would be useful to do that? I would
also like to know what could be useful to aggregate the test results.
I'm a completely newbee to Jenkins and the testing business, and the big
quantity of plugins and possibilities is a little bit overwhelming to me.
Thank you in advance for the answers.
Greetings from Cracow.
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Using-Jenkins-to-automated-testing-tp4676807.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
