-
Notifications
You must be signed in to change notification settings - Fork 474
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
🐞 - Integration Tests failing #2474
Comments
Are you using Jest in your testing? If so, make sure you check out this little newly added guide: |
Hey @waterplea, thanks for your answer. I've followed that guide already. Doesn't seem to fix the issue. |
try import {CSS} from '@ng-web-apis/common';
beforeEach(async () => {
await TestBed.configureTestingModule({
declarations: [TestTaigaWrapperComponent, FeatureRequestFormComponent],
imports: [
TuiRootModule,
ReactiveFormsModule,
TuiInputModule,
TuiTextAreaModule,
],
providers: [
{ provide: CSS, useValue: MY_MOCK_CSS }
]
})
fixture = TestBed.createComponent(TestTaigaWrapperComponent)
}) |
@splincode no luck with that fix... anyhow, it seems really obscure, right? So far, my decision was to rely on cypress for behavioral tests, where I never had a problem with Taiga, and leave Jest for Unit Testing, using mocks to avoid these issues. Not sure if it's a good approach, but I like this library, although it is giving too many headaches so far with testing. |
Another usual error I encounter is It works perfectly on |
If you don't feel like investigating this, it is okay to close it. I took an alternative path because it was making me lose too much time and in the end, I just want to test that my app behaves as I want to, which I can do with cypress. |
So it works with cypress and your original issue was with Jest? We plan to switch on Jest ourselves in the future, so we would probably bundle some sort of jest-setup to kick-start testing. Let's keep this issue open for now. |
That's right. It does work with cypress, so I have a way to test it. Count me in if I can help with that research. :) Thanks for the answers anyway. |
Which @taiga-ui/* package(s) are the source of the bug?
core, kit, cdk
Please provide a link to a minimal reproduction of the bug
No response
Is this issue blocking you?
Blocking
Description
I am having lots of problems with integration tests.
Is there a prefered way to work with tests when using Taiga Components? Is Integration tests out of the table?
This is an example:
Having the following files
I get the following error:
Angular version
14.1.1
Taiga UI version
2.60.0
Which browsers have you used?
Which operating systems have you used?
The text was updated successfully, but these errors were encountered: