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

Duplicate feature name in serenityjs report #81

Closed
vijay-kumar-singh opened this issue Aug 11, 2017 · 3 comments
Closed

Duplicate feature name in serenityjs report #81

vijay-kumar-singh opened this issue Aug 11, 2017 · 3 comments

Comments

@vijay-kumar-singh
Copy link

@vijay-kumar-singh vijay-kumar-singh commented Aug 11, 2017

Hi,
I am getting duplicate feature name in serenityjs report.

i have setup project structure in following way:
-features(Folder)
-profile(folder)
-profileAccountsDetails.feature(cucumber feature file)
-otherFeature(folder)
-otherFeature.feature(cucumber feature file)

And in feature file(profileAccountsDetails.feature):
Feature: Profile Details
As a valuable customer,
I would like to visit Profile page.......
...........
After executing i am getting duplicate title in Serenityjs report.
screen shot 2017-08-11 at 10 15 10 am

Please suggest how i can remove duplicate feature title here.

Regards,
Vijay Singh

@Baasie
Copy link

@Baasie Baasie commented Aug 17, 2017

The first profile is the capability, the same issue is probable described here to:
#75

I have the same issues atm

jan-molak added a commit that referenced this issue Oct 1, 2017
…d and appear in the report.

affects: @serenity-js/core

Please note that if your acceptance tests are not stored in the default ./features directory you
will need to set the requirementsDirectory in the Serenity/JS config.
See
http://serenity-js.org/overview/configuration.html#requirements-directory

ISSUES CLOSED: #75, #81
@jan-molak
Copy link
Member

@jan-molak jan-molak commented Oct 1, 2017

@Baasie, @vijay-kumar-singh - the latest version should address this issue. Please let me know if it's all working for you now?

@jan-molak
Copy link
Member

@jan-molak jan-molak commented Dec 16, 2017

Closing the ticket as the issue should be resolved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants