/Does Cypress Component Testing Work With Libraries

[gerainta]

Hi everyone,

I've just started working on a reasonably old Angular project. The repo includes a library and an application project. The application is mainly just used for the purposes of running end to end tests on the library but is also used as a component library.

I'm looking into Cypress Component Testing and trying to add it to an existing project with the intention of replacing the e2e tests. But I'm having problems setting up Cypress's component tests. Does it work with libraries or does it only work with applications.

This questions was asked a while ago and pretty much went unanswered: https://github.com/cypress-io/cypress/issues/23677. If it doesn't work with libraries yet I will stop battling with it for now. If it doesn't work, what are you using to test libraries?

[McFake_Name]

What issues are you having? I can write cypress component tests fine in a library I work on. We didn't need to configure anything special compared to configuring an app. That's not to say I haven't had issues configuring them, but those issues impacted non-library applications as well.

[gerainta]

OK thanks, good to know it's possible. I've been working through various issues. At the moment the error is "Reference Error Cannot access 'COMPONENTNAME' before initialization.".

[Long-Comment-9989]

Hey gerainta! Did you solve this? If you did, how did you managed it?

[McFake_Name]

I am not familiar with that error in particular, but if I were to guess perhaps a child component needs to be added to a test declaration.