JBehave
  1. JBehave
  2. JBEHAVE-267

Embedder should be responsible for all configurable aspects of story running

    Details

    • Type: Improvement Improvement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0
    • Component/s: Ant Tasks, Core, Maven Plugin
    • Labels:
      None
    • Number of attachments :
      0

      Description

      In 2.x, responsibilities are split between the StoryRunner and the Ant task/Maven plugin. E.g. the ability to skip some stories or ignore failure is configured at Ant/Maven level.

      An Embedder should instead be responsible for running stories in the same way, whatever environment it is embedded in, IDE, CLI, web.

      The Ant/Maven layer should become wafer-thin, only responsible for collecting the stories to be run, delegating to the embedder.

        Activity

        Mauro Talevi made changes -
        Field Original Value New Value
        Assignee Mauro Talevi [ maurotalevi ]
        Mauro Talevi made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Mauro Talevi made changes -
        Summary Embeddable StoryRunner should be responsible for all configurable aspects for story running StoryEmbedder should be responsible for all configurable aspects of story running
        Description In 2.x, responsibilities are split between the StoryRunner and the Ant task/Maven plugin. E.g. the ability to skip some stories or ignore failure is configured at Ant/Maven level.

        The Ant/Maven layer should become wafer-thin, only responsible for collecting the stories to be run, delegating to a configurable story runner that is the same as is used when running in other embedded environments, e.g. IDE.
        In 2.x, responsibilities are split between the StoryRunner and the Ant task/Maven plugin. E.g. the ability to skip some stories or ignore failure is configured at Ant/Maven level.

        A StoryEmbedder should instead be responsible for running stories in the same way, whatever environment it is embedded in, IDE, CLI, web.

        The Ant/Maven layer should become wafer-thin, only responsible for collecting the stories to be run, delegating to the story embedder.
        Mauro Talevi made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Mauro Talevi made changes -
        Summary StoryEmbedder should be responsible for all configurable aspects of story running Embedder should be responsible for all configurable aspects of story running
        Description In 2.x, responsibilities are split between the StoryRunner and the Ant task/Maven plugin. E.g. the ability to skip some stories or ignore failure is configured at Ant/Maven level.

        A StoryEmbedder should instead be responsible for running stories in the same way, whatever environment it is embedded in, IDE, CLI, web.

        The Ant/Maven layer should become wafer-thin, only responsible for collecting the stories to be run, delegating to the story embedder.
        In 2.x, responsibilities are split between the StoryRunner and the Ant task/Maven plugin. E.g. the ability to skip some stories or ignore failure is configured at Ant/Maven level.

        An Embedder should instead be responsible for running stories in the same way, whatever environment it is embedded in, IDE, CLI, web.

        The Ant/Maven layer should become wafer-thin, only responsible for collecting the stories to be run, delegating to the embedder.

          People

          • Assignee:
            Mauro Talevi
            Reporter:
            Mauro Talevi
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: