Support for a built-in browser runner #1019
Replies: 2 comments
-
There are some interesting challenges in this process:
Apart from that, there is a different plan, but not exactly that one: create an ecosystem with extensions such as But they still wouldn't run in the browser, but rather in the terminal (without the need for compilation). @junior-santana, could you share an example of how it is done currently or how it would be used in practice? This would help to think of an approach to make it possible (or study its feasibility) 🙋🏻♂️ |
Beta Was this translation helpful? Give feedback.
-
|
To be clear, I haven't used poku (yet), so I don't have the full context here. I assume when running in the browser, we have to compromise a few things. Currently, the setup we have uses Jasmine + Testem. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a plan to support running the tests in a browser with a built-in browser runner?
Scenario: In a VueJS project, we can mount components which will be the subject under test, then have the full context of a browser to interact with them and test how they behave and render.
It's a little more than unit testing, but far from E2E.
I'd rather keep using a real browser instead of moving to virtual DOM options, so a transition would be smoother.
Beta Was this translation helpful? Give feedback.
All reactions