Uploaded image for project: 'JBehave'
  1. JBEHAVE-588

FailingUponPendingSteps only works for normal steps, it does not do as it suggests for composite steps

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.4
    • Fix Version/s: 3.5
    • Component/s: Core
    • Labels:
      None

      Description

      Whereas as mismatching (regex) step text causes PENDING (as expected), then subsequent job failure for regular given, when or then steps, this the case for composite steps. E.g. the following ...

       
      @Given ("This matches just fine") 
      @Composite(steps = ["This matches nothing", "Perhaps this matches, perhaps it does not"]) 
      public void unimportantMethodName() { } 
      

      ... does not cause ultimate build failure.

      Moreover, the step executer continues to the next step rather than marks that as NOT PERFORMED as expected. Perhaps the two are related.

        Attachments

          Activity

            People

            • Assignee:
              maurotalevi Mauro Talevi
              Reporter:
              paulhammant Paul Hammant
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: