How do I specify TAP::Harness::Junit in the perl makefile?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a Makefile.PL using MakeMaker for my perl module like this :
#!/usr/bin/perl
use strict;
use warnings FATAL => 'all';
use 5.008;
use ExtUtils::MakeMaker;
WriteMakefile
(
NAME => 'MyModule',
AUTHOR => 'Subu',
LICENSE => 'perl',
PREREQ_PM => {
'File::Basename' => '0',
},
TEST_REQUIRES => {
'Test::More' => '0.47',
'Test::MockModule' => 'v0.170.0',
'Test::MockObject' => '1.20180705',
'Devel::Cover' => '1.31',
'Test::File' => '1.443'
},
BUILD_REQUIRES => {
'Log::Log4perl' => '1.49',
'JSON::Parse' => '0.55',
'Time::Piece' => '1.33',
'Text::CSV' => '1.97'
},
EXE_FILES => [
'src/main/perl/MyModule/main.pl'
],
test => {TESTS => 'src/test/perl/MyModule/*/*.t
src/test/perl/MyModule/*/*/*.t'}
);
I'm able to run tests using
perl Makefile.PL
make
make test
However, I would like to have the output formatted using the TAP::Harness::Junit. How do I specify that in the makefile ?
I know I can run the tests with prove
prove --formatter TAP::Formatter::JUnit *.t
But I wanted to know if there is a way I can plug that into my makefile.
perl makefile
add a comment |
I have a Makefile.PL using MakeMaker for my perl module like this :
#!/usr/bin/perl
use strict;
use warnings FATAL => 'all';
use 5.008;
use ExtUtils::MakeMaker;
WriteMakefile
(
NAME => 'MyModule',
AUTHOR => 'Subu',
LICENSE => 'perl',
PREREQ_PM => {
'File::Basename' => '0',
},
TEST_REQUIRES => {
'Test::More' => '0.47',
'Test::MockModule' => 'v0.170.0',
'Test::MockObject' => '1.20180705',
'Devel::Cover' => '1.31',
'Test::File' => '1.443'
},
BUILD_REQUIRES => {
'Log::Log4perl' => '1.49',
'JSON::Parse' => '0.55',
'Time::Piece' => '1.33',
'Text::CSV' => '1.97'
},
EXE_FILES => [
'src/main/perl/MyModule/main.pl'
],
test => {TESTS => 'src/test/perl/MyModule/*/*.t
src/test/perl/MyModule/*/*/*.t'}
);
I'm able to run tests using
perl Makefile.PL
make
make test
However, I would like to have the output formatted using the TAP::Harness::Junit. How do I specify that in the makefile ?
I know I can run the tests with prove
prove --formatter TAP::Formatter::JUnit *.t
But I wanted to know if there is a way I can plug that into my makefile.
perl makefile
add a comment |
I have a Makefile.PL using MakeMaker for my perl module like this :
#!/usr/bin/perl
use strict;
use warnings FATAL => 'all';
use 5.008;
use ExtUtils::MakeMaker;
WriteMakefile
(
NAME => 'MyModule',
AUTHOR => 'Subu',
LICENSE => 'perl',
PREREQ_PM => {
'File::Basename' => '0',
},
TEST_REQUIRES => {
'Test::More' => '0.47',
'Test::MockModule' => 'v0.170.0',
'Test::MockObject' => '1.20180705',
'Devel::Cover' => '1.31',
'Test::File' => '1.443'
},
BUILD_REQUIRES => {
'Log::Log4perl' => '1.49',
'JSON::Parse' => '0.55',
'Time::Piece' => '1.33',
'Text::CSV' => '1.97'
},
EXE_FILES => [
'src/main/perl/MyModule/main.pl'
],
test => {TESTS => 'src/test/perl/MyModule/*/*.t
src/test/perl/MyModule/*/*/*.t'}
);
I'm able to run tests using
perl Makefile.PL
make
make test
However, I would like to have the output formatted using the TAP::Harness::Junit. How do I specify that in the makefile ?
I know I can run the tests with prove
prove --formatter TAP::Formatter::JUnit *.t
But I wanted to know if there is a way I can plug that into my makefile.
perl makefile
I have a Makefile.PL using MakeMaker for my perl module like this :
#!/usr/bin/perl
use strict;
use warnings FATAL => 'all';
use 5.008;
use ExtUtils::MakeMaker;
WriteMakefile
(
NAME => 'MyModule',
AUTHOR => 'Subu',
LICENSE => 'perl',
PREREQ_PM => {
'File::Basename' => '0',
},
TEST_REQUIRES => {
'Test::More' => '0.47',
'Test::MockModule' => 'v0.170.0',
'Test::MockObject' => '1.20180705',
'Devel::Cover' => '1.31',
'Test::File' => '1.443'
},
BUILD_REQUIRES => {
'Log::Log4perl' => '1.49',
'JSON::Parse' => '0.55',
'Time::Piece' => '1.33',
'Text::CSV' => '1.97'
},
EXE_FILES => [
'src/main/perl/MyModule/main.pl'
],
test => {TESTS => 'src/test/perl/MyModule/*/*.t
src/test/perl/MyModule/*/*/*.t'}
);
I'm able to run tests using
perl Makefile.PL
make
make test
However, I would like to have the output formatted using the TAP::Harness::Junit. How do I specify that in the makefile ?
I know I can run the tests with prove
prove --formatter TAP::Formatter::JUnit *.t
But I wanted to know if there is a way I can plug that into my makefile.
perl makefile
perl makefile
edited Nov 22 '18 at 7:53
Mike
2,1702825
2,1702825
asked Nov 22 '18 at 7:48
SubuSubu
235
235
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The Makefile.PL
is primarily intended to make your modules cpan-installable. For example, make test
would be run during module installation to verify that it works correctly on the target system. For that purpose, changing the formatter (and adding an extra dependency) is not helpful.
The Makefile.PL
is not necessarily the place for your personal development workflow or for any Continuous Integration scripts. E.g. if you want to generate JUnit test reports on a Jenkins server, you might want to put the prove --formatter TAP::Formatter::JUnit *.t
command into a Jenkinsfile. If you prefer writing Makefiles, you could use a separate Makefile for your personal development scipts, though you'd have to use make -f MyMakefile test
to invoke it.
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426123%2fhow-do-i-specify-tapharnessjunit-in-the-perl-makefile%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Makefile.PL
is primarily intended to make your modules cpan-installable. For example, make test
would be run during module installation to verify that it works correctly on the target system. For that purpose, changing the formatter (and adding an extra dependency) is not helpful.
The Makefile.PL
is not necessarily the place for your personal development workflow or for any Continuous Integration scripts. E.g. if you want to generate JUnit test reports on a Jenkins server, you might want to put the prove --formatter TAP::Formatter::JUnit *.t
command into a Jenkinsfile. If you prefer writing Makefiles, you could use a separate Makefile for your personal development scipts, though you'd have to use make -f MyMakefile test
to invoke it.
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
add a comment |
The Makefile.PL
is primarily intended to make your modules cpan-installable. For example, make test
would be run during module installation to verify that it works correctly on the target system. For that purpose, changing the formatter (and adding an extra dependency) is not helpful.
The Makefile.PL
is not necessarily the place for your personal development workflow or for any Continuous Integration scripts. E.g. if you want to generate JUnit test reports on a Jenkins server, you might want to put the prove --formatter TAP::Formatter::JUnit *.t
command into a Jenkinsfile. If you prefer writing Makefiles, you could use a separate Makefile for your personal development scipts, though you'd have to use make -f MyMakefile test
to invoke it.
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
add a comment |
The Makefile.PL
is primarily intended to make your modules cpan-installable. For example, make test
would be run during module installation to verify that it works correctly on the target system. For that purpose, changing the formatter (and adding an extra dependency) is not helpful.
The Makefile.PL
is not necessarily the place for your personal development workflow or for any Continuous Integration scripts. E.g. if you want to generate JUnit test reports on a Jenkins server, you might want to put the prove --formatter TAP::Formatter::JUnit *.t
command into a Jenkinsfile. If you prefer writing Makefiles, you could use a separate Makefile for your personal development scipts, though you'd have to use make -f MyMakefile test
to invoke it.
The Makefile.PL
is primarily intended to make your modules cpan-installable. For example, make test
would be run during module installation to verify that it works correctly on the target system. For that purpose, changing the formatter (and adding an extra dependency) is not helpful.
The Makefile.PL
is not necessarily the place for your personal development workflow or for any Continuous Integration scripts. E.g. if you want to generate JUnit test reports on a Jenkins server, you might want to put the prove --formatter TAP::Formatter::JUnit *.t
command into a Jenkinsfile. If you prefer writing Makefiles, you could use a separate Makefile for your personal development scipts, though you'd have to use make -f MyMakefile test
to invoke it.
answered Nov 22 '18 at 11:38
amonamon
52.9k271128
52.9k271128
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
add a comment |
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
Thank you, that makes sense.
– Subu
Nov 22 '18 at 12:34
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426123%2fhow-do-i-specify-tapharnessjunit-in-the-perl-makefile%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown