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.

Sign up for GitHub

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

Jump to bottom

Use BDD #2

Open
jmatsushita opened this issue Mar 8, 2016 · 0 comments
Open

Use BDD #2

jmatsushita opened this issue Mar 8, 2016 · 0 comments

Comments

@jmatsushita
Copy link
Member

First do some sanity checks with regards to input/outputs with fixtures and then think of a way to test deployment side of docsmith.
jmatsushita added a commit that referenced this issue Mar 8, 2016
@jmatsushita
Beginning work on BDD. #2
ff285a1
jmatsushita added a commit that referenced this issue Mar 9, 2016
@jmatsushita
Better modularity of steps. Cloning and docsmith exec works. #2
7dad37d
jmatsushita added a commit that referenced this issue Mar 11, 2016
@jmatsushita
Tests. Needs mock repo for testing GH_TOKEN generation. #2
c0dc824
jmatsushita added a commit that referenced this issue Mar 11, 2016
@jmatsushita
Properly failing tests when promise rejects. #2
b71b35d
jmatsushita added a commit that referenced this issue Mar 11, 2016
@jmatsushita
Run cucumber tests. Pending steps. #2
22e0a39
jmatsushita added a commit that referenced this issue Mar 12, 2016
@jmatsushita
Fixed missing script tag in generated travis file. #2
de80991
jmatsushita added a commit that referenced this issue Mar 13, 2016
@jmatsushita
Refactored travis file generation, using template file. #2 #4. Deal w…
64236b0 
…ith npm based build #5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jmatsushita