Cypress auto-generates files too aggressively

[lorennorman]

• Operating System: MacOS
• Cypress Version: 0.19.2

Are you requesting a feature or reporting a bug?

Feature (usability)

Current behavior:

Cypress generates a fixture example on every run if there is no cypress/fixtures directory. A project with existing Cypress tests but no fixtures (an empty cypress/fixtures directory) will trigger this behavior for every next developer who clones it, as the empty directory isn't known to git. Whoops, that's confusing to collaborators!

Expected behavior:

I expect Cypress not to generate any files on my behalf for a project that has already had Cypress set up by my team. This might mean:

• only generating files at the time Cypress is first added
• a setting for disabling this behavior on the project
• extra setup information about using .keep files in the cypress/fixtures directory

How to reproduce the current behavior:

Delete the cypress/fixtures folder and run the tests.

Test code:

N/A

Additional Info (images, notes, stack traces, etc)

I assume this happens for other auto-generated files as well, I just happened to run into it with the fixtures directory.

[willclarktech]

Also applies to the cypress/support folder. I've had to add these folders to .gitignore and .eslintignore because the autogenerated code doesn't conform to my eslint config.

[jwld]

Bump, this is really irritating behaviour.

[jennifer-shehane]

This will be covered as part of the cypress init proposal #619

[nrhoffmann]

This is still an issue if you use cypress open.

[jennifer-shehane]

Yes, this is a duplicate of #619