cypress-realworld-app VS Svelte

Cypress documentation

The full source code of the examples shown in this article can be found here. The example web app is based on the react-note-taking-app built on top of the T3 Stack. The Cypress tests and configuration are based on the best practices documented in the cypress-realworld-app.

I’d encourage you to look at https://docs.cypress.io

Cypress is a modern, automated testing suite. It's a fully open source testing framework based on JavaScript and is built with libraries like Mocha and Chai that support BDD and TDD assertion styles. Further, using Cypress will be easy if you’re familiar with writing tests in JavaScript.

https://github.com/cypress-io/cypress-realworld-app

It's mainly about showing Cypress (which is something like Selenium or Playwright or what have you) but integrates it into a real world example with commonly used tools and frameworks.

I think the Cypress documentation is absolutely great:

https://docs.cypress.io/

One of the better things about cypress are how they create so many how-to guides for a variety of scenarios. Take implementing Cypress into a CI runners, they have guides on how to effectively use it nearly everywhere:

https://docs.cypress.io/guides/continuous-integration/ci-pro...

GitHub: https://github.com/cypress-io/cypress-realworld-app

In addition, we have also prepared over 30+ examples of real-world tests against the Real World App. This application has been around for a couple of years now, but since it contains some rather advanced concepts and examples, much of it was beyond reach for people just getting started. To solve this problem we have written in-depth articles for every example which explains line by line what each test is doing.

Cypress.io is just a test runner, but it can be paired with Testomat.io, a test management system for automated tests. Let's see how Testomat.io can answer the questions risen above. We will use Cypress Realworld App as you might have guessed, this is a good example of a project with well-written Cypress tests.

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.