JBehave
  1. JBehave
  2. JBEHAVE-716

Add an optional StoryFinder class element to @UsingPaths annotation

    Details

    • Type: Improvement Improvement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6
    • Component/s: Core
    • Labels:
    • Number of attachments :
      0

      Description

      Currently @UsingPaths is using one fixed instance of StoryFinder class.
      In order to use a custom StoryFinder class with the annotation, I would like to include an optional storyFinder element in the @UsingPaths annotation.

        Activity

        Mauro Talevi made changes -
        Field Original Value New Value
        Assignee Mauro Talevi [ maurotalevi ]
        Mauro Talevi made changes -
        Summary Add an optional StoryFinder class parameter to @UsingPaths annotation Add an optional StoryFinder class element to @UsingPaths annotation
        Issue Type New Feature [ 2 ] Improvement [ 4 ]
        Description Currently @UsingPaths is using one fixed instance of StoryFinder class.
        In order to use a custom StoryFinder class with the annotation, I would like to include an optional storyFinderClass parameter in the @UsingPaths annotation.
        Currently @UsingPaths is using one fixed instance of StoryFinder class.
        In order to use a custom StoryFinder class with the annotation, I would like to include an optional storyFinder element in the @UsingPaths annotation.
        Mauro Talevi made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Mauro Talevi made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Cristiano Gavião added a comment -

        Since we are informing the path and the StoryFinder class in the @UsingPaths, we need a runStoriesAsPaths() method without parameter in Embedder class.
        Or perhaps a new Embedder abstract class that already implements the run() method of Embeddable interface.

        Show
        Cristiano Gavião added a comment - Since we are informing the path and the StoryFinder class in the @UsingPaths, we need a runStoriesAsPaths() method without parameter in Embedder class. Or perhaps a new Embedder abstract class that already implements the run() method of Embeddable interface.
        Cristiano Gavião made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Hide
        Mauro Talevi added a comment -

        @UsingPaths is used by the AnnotatedPathRunner and the paths configured are passed to the Embedder runStoriesAsPaths(List<String>) method.

        If you want, you can use the annotated builder to get the paths directly from the annotation.

        new AnnotationBuilder(A.class).findPaths()
        

        We can devise other uses of @UsingPaths but it should be tracked by another Jira issue.

        Show
        Mauro Talevi added a comment - @UsingPaths is used by the AnnotatedPathRunner and the paths configured are passed to the Embedder runStoriesAsPaths(List<String>) method. If you want, you can use the annotated builder to get the paths directly from the annotation. new AnnotationBuilder(A.class).findPaths() We can devise other uses of @UsingPaths but it should be tracked by another Jira issue.
        Mauro Talevi made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Mauro Talevi
            Reporter:
            Cristiano Gavião
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: