We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Nowadays, cypress for angular component testing supports signals, but it does not support input signals.
import { mount } from 'cypress/angular-signals'; describe('TestComponent signal input test', () => { const myInputSignalArray = [0,1,2,3]; beforeEach(() => { mount(TestComponent, { imports: [TestComponent], providers: [provideHttpClient(), provideAnimationsAsync()], componentProperties: { myInputSignalProperty: myInputSignalArray }, }); });
Component should looks like:
import { Component, input} from '@angular/core'; ... @Component({ selector: 'test-component', standalone: true, imports: [], templateUrl: './test.component.html', styleUrl: './test.component.scss' }) export class TestComponent{ myInputSignalProperty = input<number[]>(); ...
I should be able to setup also input signal properties
Just write simple angular component with signal input property. And in cypress try to fill this signal input property with some starting mock data.
13.14.2
v22.2.0
win11
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current behavior
Nowadays,
cypress for angular component testing supports signals, but it does not support input signals.
Component should looks like:
Desired behavior
I should be able to setup also input signal properties
Test code to reproduce
Just write simple angular component with signal input property. And in cypress try to fill this signal input property with some starting mock data.
Cypress Version
13.14.2
Node version
v22.2.0
Operating System
win11
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: