Karate VS msw

This is why we need better tools which will give benefits for the added complexity. If you need to create both the feature files AND the code, it's just complexity with little benefits. But frameworks like https://github.com/karatelabs/karate or https://github.com/Endava/cats are hiding this complexity and remove the code layer entirely. Which, in my view, this is where you need to be in 2023, particularly for API testing.

- https://insomnia.rest/ - https://hoppscotch.io/ - https://github.com/karatelabs/karate - https://github.com/warmuuh/milkman

Congrats on the launch ! I'm the lead dev of [Karate](https://github.com/karatelabs/karate) and was wondering if you had come across it. I strongly agree that collaboration should be [via Git](https://www.karatelabs.io/first-class-citizens) and the IDE and traditional solutions fall short. I hope Karate's syntax passes your "memory friendly" test :) We get regular feedback is that it is easy to read and even non-programmers can pick it up. One thing I feel we do really well is chaining of HTTP requests. And we have plugins for [IntelliJ](https://plugins.jetbrains.com/plugin/19232-karate) and [VS Code](https://marketplace.visualstudio.com/items?itemName=karatela...).

Maintaining a tool like this as open-source is hard, all the best !

FWIW https://github.com/karatelabs/karate is 83% Java.

We use karate to test our fully integrated graphql backend. Has Gherkin language support.

Try Karate

Take a look at Karate.

However, I discovered a great combination that transformed my API call testing in TypeScript: Vitest and Mock Service Worker (MSW). Their well-crafted design makes them incredibly easy to use, enhancing the overall testing experience.

While mocks are effective, they require modifying the component's internal logic or mocking global functions like fetch. This can become cumbersome for complex components with numerous API interactions. Here's where MSW shines.

> For those wondering what the use case is, you must not have tried it. It does take work to set up (with each version that's less), but it can be very nice to test in isolation esp in cases where a component is under a login, the 4th page of a 10 page form, etc. Also obviously if you're working on a component library that ships without an app, Storybook can be your development and/or demo app.

I have worked with storybook extensively over the past couple of years and my team is moving away from it in favour of MSW (https://mswjs.io).

For "4th page of a 10 page form" during the development there's hot reloading which is really stable nowadays and haven't failed me, although I understand that some setups are old and it might be easier to configure Storybook than good hot reloading.

I'm not entirely sure about the testing part of it and I'd be grateful if you could elaborate. I haven't felt the need for some special setup with SB because for unit tests, I can test a deeply nested component separately. For E2E tests, I usually test the whole form.

I agree on the component library part, this is probably the only use case where Storybook is 100% justified, but I'm unconvinced about the

Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.

similar with msw.js, but fully automated

they could be network mocks (use msw)

With orval, we can also integrate the API client in our unit tests. Orval provides first class support for mocking through the (Mock Service Worker)[https://mswjs.io/] library, and it can automatically generate the MSW handlers for testing server.

Consider a hypothetical scenario where data from a list of companies within an ERP needs to be retrieved. As a personal recommendation, leverage tools like MSW for top-level mocks, which can significantly enhance the testing process.