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

Update Usage in Readme #36

Merged
merged 2 commits into from
Jun 16, 2020
Merged

Update Usage in Readme #36

merged 2 commits into from
Jun 16, 2020

Conversation

zentby
Copy link
Contributor

@zentby zentby commented Jun 15, 2020

#34

@archfz
Copy link
Owner

archfz commented Jun 15, 2020

@zentby for some reason one of the commands order changed suddenly not quite sure why https://travis-ci.com/github/archfz/cypress-terminal-report/builds/171339539; can you change that ? after you've done it i will make a patch release for this so that the npm readme is updated as well

@zentby
Copy link
Contributor Author

zentby commented Jun 15, 2020

@archfz I'm not sure what do you mean by "order changed". The last line of the test doesn't make much sense to me...

 cy.get('.breaking-get', {timeout: 1});

@archfz
Copy link
Owner

archfz commented Jun 15, 2020

@zentby that command is for breaking the test as fast as possible but it has nothing to do why the tests fail here

If you look at the end of the travis CI output this line: cy:command (K): wait @putComment from the expected spec file https://github.com/archfz/cypress-terminal-report/blob/master/test/output/out.spec.txt changed it's location. I am not sure why tough, you can move it no problem to fix the test.

@zentby
Copy link
Contributor Author

zentby commented Jun 15, 2020

@archfz I had a look at the file and test, I think the file is actually correct. Somehow the Travis run into a strange state.
image

Hence retry the CI

@archfz archfz merged commit 91fb9e5 into archfz:master Jun 16, 2020
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

Successfully merging this pull request may close these issues.

2 participants