JBehave
  1. JBehave
  2. JBEHAVE-658

WebRunner should be responsible for all running functionality (sync and async)

    Details

    • Type: Improvement Improvement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: web-3.5
    • Component/s: Web Runner
    • Labels:
      None
    • Number of attachments :
      0

      Description

      WebRunner should use the StoryManager (created by the Embedder) all the running concerns.

      In should allow both synchronous running (via Run Story, which waits for output) and asynchronous running (via Submit Story, which does not wait and delegates outputs to View Story).

      WebQueue functionality of asynchronous running is now redundant. WebQueue module should be removed.

        Activity

        Mauro Talevi made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Mauro Talevi made changes -
        Summary WebQueue should delegate to Embedder all running functionality WebQueue and WebRunner should use StoryManager for all running functionality
        Description WebQueue should not be concerned with parsing nor filtering. It should delegate to the Embedder all the running concerns WebQueue and WebRunner should not be concerned with parsing nor filtering. It should use the StoryManager (created by the Embedder) all the running concerns.
        Component/s Web Runner [ 14122 ]
        Mauro Talevi made changes -
        Summary WebQueue and WebRunner should use StoryManager for all running functionality WebRunner should use StoryManager for all running functionality
        Description WebQueue and WebRunner should not be concerned with parsing nor filtering. It should use the StoryManager (created by the Embedder) all the running concerns. WebRunner should not be concerned with parsing nor filtering. It should use the StoryManager (created by the Embedder) all the running concerns.
        Mauro Talevi made changes -
        Summary WebRunner should use StoryManager for all running functionality WebRunner should be responsible for all running functionality (sync and async)
        Description WebRunner should not be concerned with parsing nor filtering. It should use the StoryManager (created by the Embedder) all the running concerns. WebRunner should use the StoryManager (created by the Embedder) all the running concerns.

        In should allow both synchronous running (via Run Story, which waits for output) and asynchronous running (via Submit Story, which does not wait and delegates outputs to View Story).

        WebQueue functionality of asynchronous running is now redundant. WebQueue module should be removed.
        Component/s Web Queue [ 14701 ]
        Mauro Talevi made changes -
        Resolution Fixed [ 1 ]
        Status In Progress [ 3 ] Resolved [ 5 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved: