Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-30083

Undefined steps should not be considered always failure

      Undefined steps should not be considered always failure, as this behaviour is controlled by the "--strict" parameter passed to Cucumber.

          [JENKINS-30083] Undefined steps should not be considered always failure

          Chris Andrew created issue -
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 165166 ] New: JNJira + In-Review [ 181863 ]
          James Nord made changes -
          Assignee Original: James Nord [ teilo ]

            Unassigned Unassigned
            chrisandrew Chris Andrew
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: