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

Seems cypress ci does not respect or handle integrationFolder parameter #164

Closed
bahmutov opened this issue Jun 13, 2016 · 2 comments
Closed
Assignees
Labels
cli type: enhancement Requested enhancement of existing feature

Comments

@bahmutov
Copy link
Contributor

When passing custom path to the integration folder (to allow running just some tests), cypress just initializes the Kitchen Sink example and runs its own tests, not mine.

@brian-mann
Copy link
Member

What's happening here is that when cypress does not detect any cypress tests it's seeding the example kitchen sink and running those tests.

We need to do two things better:

  1. Never seed tests when running cypress ci
  2. If Cypress cannot detect any tests it should error and indicate the exact path it searched where there were no tests.

However this was likely caused by running cypress ci in the wrong cwd and if you hypothetically update this (or pass --config options) it will work correctly.

@brian-mann brian-mann added this to the 0.16.3 milestone Jun 14, 2016
@brian-mann brian-mann self-assigned this Jun 14, 2016
@brian-mann brian-mann removed this from the 0.16.3 milestone Jun 16, 2016
@jennifer-shehane jennifer-shehane added the type: enhancement Requested enhancement of existing feature label Oct 4, 2016
@jennifer-shehane
Copy link
Member

Closing - added suggestion about never seeding when running cypress ci to #619

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli type: enhancement Requested enhancement of existing feature
Projects
None yet
Development

No branches or pull requests

3 participants