Inhttps://github.com/ReadAlongs/Web-Component we are, in theory, using@nx/jest a.k.a. @nrwl/jest which, I believe, requires Jest 28 (it's really hard to keep track of all these versions of everything...)

In practice of course this doesn't really work, so we just fall back on end-to-end testing with Cypress, which does work, consistently.

In our case, we rely on Nx to handle our monorepo and all our unit testing and e2e tests have been written with Jest and Puppeteer, following Stencil documentation. Unfortunately, we must stick to Nx 14 because Stencil supports only up to Jest 27.
Nx is currently on version 16, from the previous version (v15) Nx has released a lot of improvements for monorepos which we cannot take advantage of. Overriding Jest is not ideal because it could break with other stuff in the Nx ecosystem and we prefer Jest and Puppeteer over Cypress.
We have been thinking many times about dropping Stencil because of the lack of support in this matter. I feel is unfair not to be able to access new features and functionalities because something is holding you back to upgrade, which is not sustainable for anyone.

We also use Stencil within an NX monorepo. For all unit tests we use jest. For e2e tests Cypress. Our main frontend framework for almost all applications is Angular. The UI components for our mobile apps are based on Ionic and Stencil. The UI library for our newer web apps are written entirely in Angular, as this involves less configuration work and incopatibilities for us. Since we are working with the current version of NX, we had to disable unit-tests for the stencil components in the pipeline and try to catch this as much as possible with Cypress tests. Of course, this is not a satisfactory permanent state.

I am waiting eagerly for jest > 27 support. I prefer to run stencil tests with plainjest instead of thestencil test command, because I also want to run tests using my IDE and withwallaby.js.

I do not care for pupeteer, instead I prefer to run integration test style tests using jest andtesting-library. An officialtesting-library/stencil would be awesome.testing-library/dom works partially, but not very well in many cases.

For e2e tests I am usingplaywright. e2e tests should not care for the frameworks used underneath.

I'm working on a Stencil project and a component is using a custom decorator (@ ResponsiveCssClasses()) to apply responsive classNames to a component:

exportclassMyTable{    @Element() @ResponsiveCssClasses()hostEl:HTMLMyTableElement;...

When I run the tests, I get a failure:

    ReferenceError: _hostEl_decorators is not defined

Unsure if this is Jest causing this issue (if so, if it's an older version of Jest), or if it's just the component 🤔

Hey guys,
are you running your test on different browsers? If yes, how? Thanks!