But we are stepping as always on the shoulders of giants

Really well done! I'm looking forward to experimenting with Cypress for some updates to a design system we work with at Letterhead, thanks to that talk!

@User they're so sneaky tho right?!

You almost don't notice you've gotten test coverage 😼

@User fair warning. We are in early stages

If you can get your project's webpack config to work, then you should be good to go, but that's the spot we're struggling w right now

Our API itself is very stable... just the initial bundling setup needs some better DX

We're pretty early-stage to, as a company and as an app, so that might not be a bad thing.

Yeah. Any fresh boilerplate will work fine

just like mismatched webpack 3 and various other plugin versions get a little weird. That's what we're working through this week/next two weeks

I'll keep that in mind!

Yep. We're here for you if you need anything. We also likely have a boilerplate for it... need to get those cataloged in a README or in the docs

To be honest, I'm pretty sure this would be the first any testing we'd be brining into our design system, so it doesn't need to necessarily live in said design system and we can be pretty flexible with it.

I'm excited. 😻

We currently do testing in Jest, and the docs/styleguide is Storybook. The docs part is fine, but testing in Jest can be a challenge at times and, like Jess said, you're sort of assuming that your tests run fine, even if they pass. You're betting that you didn't make a mistake anywhere or overlooked something. You can probably mitigate quite a bit by using libraries like xstate, but it's still a good idea to "test like a user would", so Cypress is a welcome tool. At some point we'll probably leave Jest test for pure unit tests and switch to Cypress for component tests. We'll be using it for integration/e2e tests anyway.

Yeah @User that's what we're imagining as the future. I do think that people will tend toward rolling their own Styleguide and docs system that is more powerful than storybook.

Storybook's main value (imho) is acting as this visual REPL

the fact that it does documentation and styleguides is almost an aside, yknow?

I definitely think Jest still has a place in unit testing. 🙂

Yeah it seems to be slowly transforming as to what its purpose is (Storybook). I find it very useful for our component library and even to dev against, but if easier or better ways become available, I usually switch at some point haha.

@User I love storybook (I am even a contributor) but if you want to customize the layout, you have to do it in React

not very fun for developers of Vue components

I prefer to adopt what Chakra, VUetify and Bootstrap have done

Use a vuepress/vitepress/nuxt site and make it good looking

Yeah I agree. We actually started out with vitepress, but it was incredibly buggy and feature poor, so not really useful (2/3 months ago or so) Didn't want to do VuePress because our stack is Vite/Vue3, so really not a ton of options

Also at some point you have to choose something that at least works, can't change forever 😄

yes that is true

Hello 👋 , I am working with Cypress and I have had some doubts, where can I send them?

@User Depending on wether they are "issues" with Developer Experience -> Github Issues or if they are doubts about you code patterns -> #763105090679865354 or if they are doubts about the future of what we do -> post here or if you are only using e2e -> #755913900024791046 or if you want to give us feedback on component testing -> #755921564108587038

Great! Ty