Added formatting

I'm getting this error too. Does anybody knows how to solve that ?

Guys, someone could solved this issue?
Thanks in advance...

I noticed a problem with the attached cucumber.json. It seems that if a Feature file only has an outline, there are no results saved in the file. So I wrote an example Feature file that would have basic scenario and a failing scenario along with the Scenario Outline.

Feature: Sample test
  Scenario Outline: Parsing scenarios with multiple examples
    Given I navigate to the home page
    Then I see the text 'Home'
  Examples:
      | a | b |
      | 1 | 2 |
  Scenario: Basic
    Given I navigate to the home page
    Then I see the text 'Home'
  Scenario: Basic failure
    Given I navigate to the home page
    Then I see the text 'Hacienda'

attaching a new json file: cucumber_with_outline_and_basic_scenario.json

json result file from a Feature file that has one Scenario Outline and 2 Scenarios.

There is a bug [1] in gherkin at the core of this bug. Apparently Gherkin json output does not contain results for scenario outlines. So this bug will not be able to show the results of scenario outlines. But it can better handle the ScenarioOutline event in the GherkinCallback to not fail with exception if the json is missing results (work around the year old bug [1] in Gherkin)

[1] https://github.com/cucumber/gherkin/issues/165

Hi James, thanks for the answer. I understood the point, but its sorry that I have to use the "scenario" to get the report i need, cuz my feature just work fine today without this. I saw that the link of the issue was 2 years ago, may by this time they have solved, do you know?

Thanks for all the information and your time spent.

My use of this plugin is parsing json from a Ruby on Rails project. So the end result will still be missing results from Scenario Outlines because of that old, persistent bug in Gherkin (#165 referenced earlier).

My primary language is Java. I've worked with other Jenkins plugins. I looked at this problem. My fix would require a lot of refactoring around the org.jenkinsci.plugins.cucumber.jsontestsupport.GherkinCallback class to incorporate the State Pattern and a logging framework.

I might be able to put together a pull request.

There are 3 options
1) fail any scenario outlines if a result isn't present. (any jobs with these will then be marked as failed)
2) pass any scenario outlines if a result isn't present. (any failures will be silently passed which is not good)
3) barf like we do now - and get fixed upstream.

3 is the only viable solution in my eyes and this should be fixed upstream in the ruby cucumber implementation.

This would be marked as wont-fix as this is not a bug - we have been supplied with malformed input - but leaving open incase anyone else hits this so they can see where the real cause is. (will close when upstream is fixed).

Is there any news?

teilo i extended plugin with additional options. If developer unsure about features - then they should be configurable .
https://github.com/jenkinsci/cucumber-testresult-plugin/pull/2

• Changed java stacktrace to pretty build Failure with additional information.
• Removed System.out.println() - never use it plugins. There is "manage jenkins" -> "system logger".
• Error message describes what is really wrong and notes this issues. So after merge close this issue.
• Added aditional checkbox for ignoring not existed step results - this fixed my case, so now i may use it.

PR only has no tests atm...

Have you tried with a fixed version of cucumber instead?
This has apparently been fixed upstream.

Of course tried. We are using grunt-cuke-tree that we can't update atm. (Tt's not just bump version in package.json).

Code changed in jenkins
User: Kanstantsin Shautsou
Path:
src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParser.java
src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/GherkinCallback.java
http://jenkins-ci.org/commit/cucumber-testresult-plugin/14c313da7f51527df7468f39140a27ff44ffc33c
Log:
JENKINS-21835 Don't print stacktrace. Print friendly log.

workaround enabled.

Enabling this may cause tests that have failed to not cause the build to be marked as unstable - but there is no information about the result so there is nothing else that can be done.

The cause of the issue has fixes upstream - so it is a matter of getting those fixes into all the relevant tools to get a real fix.

Unfortunately https://github.com/cucumber/cucumber/issues/700 is a 404. Does anyone know which issue that was, and/or which Cucumber version (if any) contains the fix?

Ok, the cucumber repo was renamed to cucumber-ruby and gherkin was renamed to gherkin2. The links above are now:

https://github.com/cucumber/cucumber-ruby/issues/700

https://github.com/cucumber/gherkin2/issues/165

dserodio thanks for the detective work. If you find the versions with fixes can you comment here?