cypress-io
Angular schematic generate component testing files by default
Current behavior
By answering 'No' to component testing support when adding Cypress for Angular with ng add @cypress/schematics, the schematic added still overrides the generic component schematic and creates a cy.ts test file in place of the spec.ts file.
Desired behavior
If Component Testing support is not chosen by adding Cypress, creating a new component with ng g generate should create a spec.ts file by using ng generate component schematic.
Test code to reproduce
- create a Angular project
npx -p @angular/cli ng new projectName - move to your root folder with
cd projectName - add Cypress with
ng add @cypress/schematics - answer 'No' to component testing support
- create a Angular component with
ng generate component home - a
home-component.cy.tsfile is created.
Cypress Version
13.0.0
Node version
v18.16.1
Operating System
macOS 13.5
Debug Logs
No response
Other
No response
I'm seeing this, too. Angular CLI v15.1.6, Cypress v12.10.0.
Of note (perhaps) is that I didn't have this problem when I was using Angular CLI v13.3.0.
I started having the same problem at some point in an old project and was able to "fix" it by reordering schematics in angular.json file.
Before:
"cli": {
"schematicCollections": [
"@cypress/schematic",
"@angular-eslint/schematics",
"@schematics/angular"
],
"analytics": false
}
After:
"cli": {
"schematicCollections": [
"@schematics/angular",
"@angular-eslint/schematics",
"@cypress/schematic"
],
"analytics": false
}
I started having the same problem at some point in an old project and was able to "fix" it by reordering schematics in
angular.jsonfile.Before:
"cli": { "schematicCollections": [ "@cypress/schematic", "@angular-eslint/schematics", "@schematics/angular" ], "analytics": false }After:
"cli": { "schematicCollections": [ "@schematics/angular", "@angular-eslint/schematics", "@cypress/schematic" ], "analytics": false }
Thankyou it worked!
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.
