Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steps marked as pending, after reorganising testrunners #1774

Closed
eriklumbela opened this issue Aug 13, 2019 · 4 comments
Closed

Steps marked as pending, after reorganising testrunners #1774

eriklumbela opened this issue Aug 13, 2019 · 4 comments
Labels

Comments

@eriklumbela
Copy link

background
I have the following Serenity JBehave project layout: (in the testrunners directory are my classes extending SerenityStory)

src
|-- test
    |-- java
        |-- com.company.team
            |-- definitionsteps
            |-- usersteps
            |-- testrunners
    |-- resources
        |-- stories
            |-- epic1
            |-- epic2

problem
Once I try to reorganise my testrunners into subfolders, so that it reflects resources/stories/{epics} all my steps are marked as PENDING.
In the documentation I read that:

Serenity will run any JBehave stories that it finds in the default directory location. By convention, it will look for a stories folder on your classpath, so ‘src/test/resources/stories’ is a good place to put your story files.

So I guessed reorganising shouldn't resolve into PENDING steps.
What do I need to configure to prevent this from happening?

reproduce

src
|-- test
    |-- java
        |-- com.company.team
            |-- definitionsteps
            |-- usersteps
            |-- testrunners
                |-- epic1
                |-- epic2
    |-- resources
        |-- stories
            |-- epic1
            |-- epic2
@eriklumbela
Copy link
Author

@wakaleo Have you got any suggestions how to solve this?

@wakaleo
Copy link
Member

wakaleo commented Sep 2, 2019

Not really. It sounds like a project configuration issue of some kind - maybe the JBehave runners aren't finding the step definition methods.

@eriklumbela
Copy link
Author

Thanks for your fast reply. Too bad. Does this also mean, this is supposed to work out of the box.
(Then I guess, I have to to go over the pom.xml and figure out what's wrong)

@wakaleo
Copy link
Member

wakaleo commented Sep 3, 2019

Looking at your project structure, you may need the test runner classes to be in the top level package for the default paths to work.

@wakaleo wakaleo closed this as completed Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants