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

Migrate legacy_features into features directory #408

Closed
mattwynne opened this issue Mar 25, 2013 · 11 comments
Closed

Migrate legacy_features into features directory #408

mattwynne opened this issue Mar 25, 2013 · 11 comments

Comments

@mattwynne
Copy link
Member

This is confusing for contributors. There's no reason we can't get started now, but I want this to be on the checklist for 2.0

For context, the 'legacy' directory contains features that were written before aruba. Many of them will only require a small amount of work to port them to aruba, some will need more work, some should probably just be deleted.

@rdvdijk
Copy link

rdvdijk commented Mar 27, 2013

This confused me as well. I didn't even know about aruba before I read about it here.

@tooky tooky mentioned this issue Mar 29, 2013
mattwynne added a commit that referenced this issue Mar 29, 2013
As suggested in #408, this adds a signpost until do the work in #408 to
fix the actual broken window.
@mattwynne
Copy link
Member Author

I just realised, working on #358, that rake cucumber is no longer running rake legacy_features. Haven't worked out why yet, but this has probably been happening for some time.

mattwynne added a commit that referenced this issue May 6, 2013
@mattwynne
Copy link
Member Author

@tooky @os97673 I think we need to make this ticket our top priority so we know that our refactoring work is safely covered by tests.

mattwynne added a commit that referenced this issue May 6, 2013
I'm commiting this into master, even though I know it
will break the build, because we should have had this
running all along. We should not release code from master
without checking each of these failures.
@aslakhellesoy
Copy link
Contributor

On Monday, May 6, 2013, Matt Wynne wrote:

I just realised, working on #358cucumber/common#358,
that rake cucumber is no longer running rake legacy_features. Haven't
worked out why yet, but this has probably been happening for some time.

Did you try to git blame this? It would be nice to find out when it broke
so we can improve developer docs / build script comments and prevent it
from happening again.

P.S. if it was me please blame Oleg ;-P

Aslak


Reply to this email directly or view it on GitHubhttps://github.com/cucumber/common/issues/408#issuecomment-17476206
.

@mattwynne
Copy link
Member Author

@aslakhellesoy it's hard to use git blame for this as what we need to analyse is historical travis output - when it stopped doing both feature runs. Or I guess we could just bisect the git history.

I suspect it might have something to do with #400 but I did some quick testing and couldn't really see why it would have caused it. I don't understand enough about Rake's API, but it seemed that the first task (rake features) was causing rake to exit (with status code 1) despite having had no errors.

@chrismdp
Copy link

PRs #459, #460, #461, #462, #463, #464 and #465 all moving features to the new structure.

@mattwynne
Copy link
Member Author

Done! Big thanks to @jimvm.

@os97673
Copy link
Member

os97673 commented Oct 2, 2013

Done! Big thanks to @jimvm.

So, should it be closed? ;)

@tooky
Copy link
Member

tooky commented Oct 2, 2013

\o/ great work @jimvm

@tooky tooky closed this as completed Oct 2, 2013
@jimvm
Copy link
Contributor

jimvm commented Oct 2, 2013

Glad I could help!

Somewhat related, what about the fixtures directory? I don't think the json, self_test, and steps_library are in use anymore. Maybe these can be removed?

mattwynne added a commit that referenced this issue Oct 2, 2013
@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

7 participants