I figured it out. In my Jenkins project, I was adding the path/pattern to the Behat output files as a 'JUnit Pattern' under 'Publish testing tools result report'. Instead, I added the path/pattern under 'Publish JUnit test result report', and now it works. Shouldn't both of those essentially be the same thing, though? I'm not sure why one works and one doesn't! Oh well, at least it's working now :)
Matt On Feb 8, 1:30 am, "Matt L." <[email protected]> wrote: > Is anyone on here currently using Behat with Jenkins? I'm outputting > JUnit-style XML reports from Behat, and I have Jenkins set up to read > the Behat report as a JUnit pattern, however Jenkins complains that > the report is invalid: > > [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the > pattern 'build/logs/behat/*.xml' relative to '/var/lib/jenkins/jobs/ > project/workspace' for the testing framework 'JUnit'. > [xUnit] [ERROR] - The result file '/var/lib/jenkins/jobs/project/ > workspace/build/logs/behat/TEST-authentication.xml' for the metric > 'JUnit' is not valid. The result file has been skipped. > > Here's what the report looks like: > > <?xml version="1.0" encoding="UTF-8"?> > <testsuite errors="0" failures="0" name="User sessions" file="/var/lib/ > jenkins/jobs/project/workspace/application/tests/features/ > authentication.feature" tests="12" time="66.864949"> > <testcase classname="User sessions" name="Login" time="40.857683"> > </testcase> > <testcase classname="User sessions" name="Logout" > time="25.896327"> > </testcase> > </testsuite> > > ...which looks fine to me. Any idea why it's getting skipped? > > I'm using Behat version 2.3.2, and Jenkins version 1.424.2. > > Thanks!
