Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Sometimes when we set up a context or cause an event to happen, it's nice to clean up any changes so that we don't affect other tests running.

      No idea how to make the undoable work, but doesn't stop me wanting it!

        Activity

        Hide
        Mauro Talevi added a comment -

        It strikes me that one may want a "undoing" after a scenario - but not during the execution of the same scenario.
        In this case the @AfterScenario proposed in JBEHAVE-129 seems the way to go.

        Show
        Mauro Talevi added a comment - It strikes me that one may want a "undoing" after a scenario - but not during the execution of the same scenario. In this case the @AfterScenario proposed in JBEHAVE-129 seems the way to go.
        Mauro Talevi made changes -
        Field Original Value New Value
        Fix Version/s The Distant Future [ 13303 ]
        Hide
        Mauro Talevi added a comment -

        Resolving as duplicate of JBEHAVE-129, until someone comes up with a more elaborate use case.

        Show
        Mauro Talevi added a comment - Resolving as duplicate of JBEHAVE-129 , until someone comes up with a more elaborate use case.
        Mauro Talevi made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Duplicate [ 3 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Elizabeth Keogh
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: