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

Warn or fail if duplicate features are detected #165

Closed
jvans opened this issue Jan 22, 2012 · 4 comments
Closed

Warn or fail if duplicate features are detected #165

jvans opened this issue Jan 22, 2012 · 4 comments
Milestone

Comments

@jvans
Copy link

jvans commented Jan 22, 2012

When I ran my single scenario test from Maven using Main, the generated report.js had my scenario listed twice. I will see if I can isolate this a little further to get a clearer picture of what is going on.

@jvans
Copy link
Author

jvans commented Jan 23, 2012

Okay, figured out why this happens. If the feature path provided finds the same feature file twice (i.e. running from the root of your project with maven sees both src and target directories) then of course it reports the results of both feature scenarios. (Face a little red at the moment). I am not sure there is a way to prevent this. May want to warn folks about this somewhere in the documentation. If I made the mistake, it would seem possible that others might as well.

@aslakhellesoy
Copy link
Contributor

I renamed this issue. Possible solution: Build a checksum (MD5) of the feature source and store in a map: checksum->feature path

If a duplicate checksum is detected, raise an error.

@jvans
Copy link
Author

jvans commented Jan 26, 2012

Your call on renaming, but I try to describe the problem in the title rather than the solution, because I have found that on teams this pre-supposes the solution which may not necessarily be the right one.

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants