Added formatting

Change By: James Wilson (17/Feb/14 5:38 PM)
Description: What we did:
Ran minimal cucumber feature test with Jenkins
:  
{code:title=Feature}
Feature: Sample Test
  Scenario Outline: Parsing scenarios with multiple examples
    Given I navigate to the root page
    Then I see the text 'home page'
    Examples:
    | a | b |
    | 1 | 2 |
{code}

By a shell build step:
{code:title=shell build}
#!/bin/bash
# Set up RVM (Ruby 2.0)
. ~/.bashrc
set -e
CUCUMBER_OPTS='-f json -o cucumber.json features/sample.feature' rake cucumber
{code}

What we got:
[::1::]

What we expected:
No error, parsing of cucumber.json containing results from scenario outlines.

[::1::]
{code:title=Output}
/var/lib/jenkins/.rvm/rubies/ruby-2.0.0-p353/bin/ruby -S bundle exec cucumber -f json -o cucumber.json features/sample.feature
Using the default profile...
Feature: Sample Test

  Scenario Outline: Parsing scenarios with multiple examples # features/sample.feature:2
    Given I navigate to the root page                        # features/step_definitions/navigation_steps.rb:15
    Then I see the text 'home page'                          # features/step_definitions/study_admin.rb:23

    Examples: 
      | a | b |
      | 1 | 2 |

1 scenario (1 passed)
2 steps (2 passed)
0m1.080s
Xvfb stopping
Archiving artifacts
[Cucumber Tests] Parsing results.
[Cucumber Tests] parsing cucumber.json
ERROR: Failed to archive cucumber reports
java.io.IOException: Failed to parse Cucumber JSON
at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:99)
at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:44)
at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl$ParseResultCallable.invoke(DefaultTestResultParserImpl.java:161)
at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl$ParseResultCallable.invoke(DefaultTestResultParserImpl.java:107)
at hudson.FilePath.act(FilePath.java:914)
at hudson.FilePath.act(FilePath.java:887)
at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl.parse(DefaultTestResultParserImpl.java:101)
at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:116)
at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.perform(CucumberTestResultArchiver.java:93)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
at hudson.model.Run.execute(Run.java:1703)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberModelException: Step received before previous step handled!
at org.jenkinsci.plugins.cucumber.jsontestsupport.GherkinCallback.step(GherkinCallback.java:160)
at gherkin.formatter.model.Step.replay(Step.java:68)
at gherkin.JSONParser.step(JSONParser.java:106)
at gherkin.JSONParser.parse(JSONParser.java:51)
at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:94)
... 17 more
Build step 'Publish Cucumber test result report' changed build result to FAILURE
Finished: FAILURE

{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to