TestRail.pm 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120
  1. # ABSTRACT: Upload your TAP results to TestRail in realtime
  2. # PODNAME: App::Prove::Plugin::TestRail
  3. package App::Prove::Plugin::TestRail;
  4. use strict;
  5. use warnings;
  6. use utf8;
  7. use File::HomeDir qw{my_home};
  8. use TestRail::Utils;
  9. =head1 SYNOPSIS
  10. `prove -PTestRail='apiurl=http://some.testlink.install/,user=someUser,password=somePassword,project=TestProject,run=TestRun,plan=TestPlan,configs=Config1:Config2:Config3,version=0.014' sometest.t`
  11. =cut
  12. =head1 DESCRIPTION
  13. Prove plugin to upload test results to TestRail installations.
  14. Accepts input in the standard Prove plugin fashion (-Ppluginname='key=value,key=value,key=value...'), but will also parse a config file.
  15. When fed in prove plugin style, key=value input is expected.
  16. If \$HOME/.testrailrc exists, it will be parsed for any of these values in a newline separated key=value list. Example:
  17. apiurl=http://some.testrail.install
  18. user=someGuy
  19. password=superS3cret
  20. project=TestProject
  21. run=TestRun
  22. plan=GosPlan
  23. configs=config1:config2:config3: ... :configN
  24. version=xx.xx.xx.xx
  25. case_per_ok=0
  26. step_results=sr_sys_name
  27. spawn=123
  28. sections=section1:section2:section3: ... :sectionN
  29. autoclose=0
  30. encoding=UTF-8
  31. Note that passing configurations as filters for runs inside of plans are separated by colons.
  32. Values passed in via query string will override values in \$HOME/.testrailrc.
  33. If your system has no concept of user homes, it will look in the current directory for .testrailrc.
  34. See the documentation for the constructor of L<Test::Rail::Parser> as to why you might want to pass the aforementioned options.
  35. =head1 OVERRIDDEN METHODS
  36. =head2 load(parser)
  37. Shoves the arguments passed to the prove plugin into $ENV so that Test::Rail::Parser can get at them.
  38. Not the most elegant solution, but I see no other clear path to get those variables downrange to it's constructor.
  39. =cut
  40. sub load {
  41. my ($class, $p) = @_;
  42. my $app = $p->{app_prove};
  43. my $args = $p->{'args'};
  44. my $params = {};
  45. #Only attempt parse if we aren't mocking and the homedir exists
  46. my $homedir = my_home() || '.';
  47. $params = TestRail::Utils::parseConfig($homedir) if -e $homedir && !$ENV{'TESTRAIL_MOCKED'};
  48. my @kvp = ();
  49. my ($key,$value);
  50. foreach my $arg (@$args) {
  51. @kvp = split(/=/,$arg);
  52. if (scalar(@kvp) < 2) {
  53. print "Unrecognized Argument '$arg' to App::Prove::Plugin::Testrail, ignoring\n";
  54. next;
  55. }
  56. $key = shift @kvp;
  57. $value = join('',@kvp);
  58. $params->{$key} = $value;
  59. }
  60. $app->harness('Test::Rail::Harness');
  61. $app->merge(1);
  62. #XXX I can't figure out for the life of me any other way to pass this data. #YOLO
  63. $ENV{'TESTRAIL_APIURL'} = $params->{apiurl};
  64. $ENV{'TESTRAIL_USER'} = $params->{user};
  65. $ENV{'TESTRAIL_PASS'} = $params->{password};
  66. $ENV{'TESTRAIL_PROJ'} = $params->{project};
  67. $ENV{'TESTRAIL_RUN'} = $params->{run};
  68. $ENV{'TESTRAIL_PLAN'} = $params->{plan};
  69. $ENV{'TESTRAIL_CONFIGS'} = $params->{configs};
  70. $ENV{'TESTRAIL_VERSION'} = $params->{version};
  71. $ENV{'TESTRAIL_CASEOK'} = $params->{case_per_ok};
  72. $ENV{'TESTRAIL_STEPS'} = $params->{step_results};
  73. $ENV{'TESTRAIL_SPAWN'} = $params->{spawn};
  74. $ENV{'TESTRAIL_SECTIONS'} = $params->{sections};
  75. $ENV{'TESTRAIL_AUTOCLOSE'} = $params->{autoclose};
  76. $ENV{'TESTRAIL_ENCODING'} = $params->{encoding};
  77. return $class;
  78. }
  79. 1;
  80. __END__
  81. =head1 SEE ALSO
  82. L<TestRail::API>
  83. L<Test::Rail::Parser>
  84. L<App::Prove>
  85. L<File::HomeDir> for the finding of .testrailrc
  86. =head1 SPECIAL THANKS
  87. Thanks to cPanel Inc, for graciously funding the creation of this module.