-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Add cucumber feature to test for bonafide theme gems #5384
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
Conversation
34968c8
to
e71e09f
Compare
I'd like to drop the entire commit related to theme-gem fixture now that this test runs against the theme dir scaffolding generated by |
e71e09f
to
1d6e7b0
Compare
squashed and rebased.. |
(Will review once Travis is passing.) |
this cucumber feature follows the likely steps a theme designer would take to build a Rubygem of his theme starting from the scaffolding generated by `jekyll new-theme` command and further checks if the gem built actually has the files he planned to include.
8b558d1
to
1fb4dce
Compare
updated against HEAD and got travis to pass 🎉 |
When I decide to build the theme gem | ||
Then I should get a zero exit status | ||
When I run git add . | ||
Then I should get a zero exit status |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These check the exit status of the Jekyll build, I think. They'll have to be updated to see what the latest command was and read its build status.
Sure! Thanks! @jekyllbot: merge +dev |
Adds a cucumber feature to follow the steps a user would take to build a theme gem and check if it is ready for distribution using theme generated by
jekyll new-theme
Ref: #5362
/cc @parkr