uvu VS felte

Last but not least important are ava, uvu and tape; they are a really light and fast test runners.

Vitest: A Vite-native unit test framework. (alternative: Jest, uvu)

Most important here is not to forget to include test.run() at the end… I’ve done that a few times 😅. Notice how we are able to use aliases in lines 1–3. You can see the full range of assert methods available in the uvu docs.

For the past few weeks I’ve taken the (arguably pointless) work of migrating Felte from using Jest to uvu. This is a really tedious work by itself, but one of details that would have made this work even more tedious is that Jest prefers assertions to the style of expect(…).toBe* while uvu gives you freedom to choose any assertion library, although there’s an official uvu/assert module that comes with assertions to the style of assert.is(value, expected).

Hello everyone, I'm using uvu for testing. And installed c8 for coverage. Yet it doesn't seem to be able to pick up test .svelte files. Does anyone knows how to achieve this or any other way of getting .svelte files coverage? Thanks

Yes! There’s even an example test written for the svelte counter demo in the repo’s examples!

uvu is what I’d recommend.

I really enjoy Ava [1] or anything assert-tape-like [2]. "uvu" [3] is getting a lot of love lately, but it's very feature limited and much of it's touted advantages are at the detriment to feature set.

[1] https://github.com/avajs/ava

[2] https://github.com/substack/tape

[3] https://github.com/lukeed/uvu

Jest is great for front-end (or full stack integration) testing, but I feel it's specialized for that use-case and doesn't always play nice with backend/middle-tier testing needs.

For Node, I lean towards UVU by @lukeed due to its simplicity. Its lightweight, fast, supports ESM out of the box. It feels like an easier to setup modern Mocha (without the wide array of plugins).

How does it compare to Felte?

Don’t know if it can help, but I discovered this only recently, which was really missing for me with svelte: https://felte.dev/

I’ve been experimenting with web components in order to build a wrapper for Felte that can easily be used with vanilla JS. One of Felte’s features is the ability to use custom field components that are not based on the browser’s native inputs (input, textarea, select). The example I show is a div with an attribute [contenteditable=“true”]. While testing this experiment I found some weird behaviour coming from Firefox: while I could perfectly click each field and type of it, if I tried to use the form only using the keyboard (tabbing to each field) the focus moved but trying to type would always result in the text being added to the first field I focused.

There’s an example on Felte’s repo setting this up!

Ah. Of course 😅. mwc-textfield is not a native input. Felte relies on native inputs. You can use createField (by creating your own "wrapper" Svelte component that will render your ) or... better yet... you can experiment with what I've been working for the past weeks.

For the past few weeks I’ve taken the (arguably pointless) work of migrating Felte from using Jest to uvu. This is a really tedious work by itself, but one of details that would have made this work even more tedious is that Jest prefers assertions to the style of expect(…).toBe* while uvu gives you freedom to choose any assertion library, although there’s an official uvu/assert module that comes with assertions to the style of assert.is(value, expected).

After more than a year of work, I am proud to announce the release of version 1.0.0 of Felte!