howToTestFE

Site/course on teaching how to write tests, mostly about frontend tests in React but also just generally things like Vitest/Jest https://howtotestfrontend.com/courses/jest-vitest-fundamenta...

+1 very confusing name for another mongodb compatible db.

Yep. I think there are so many new apps, when I run a `npx skills add ...` , the list of what tools (like claude code, open code, etc) to install skills in is getting larger every time I use it.

I will check it out though.

100%. its a horrible code smell, and AI loves to jest.mock (or vi.mock()). (The most recent blog post on my site covers this as one of the things to look out for in AI generated tests...)

in JS (with Jest/Vitest) it is far too easy to call mock()...

yup vitest is great (my default choice for new projects).

vitest browser mode is really nice too. (new-ish feature, although at this point it isn't exactly new).

learn step by step the main features of both Jest and Vitest (they're very similar for most common usages) in these interactive4 lessons

Blog post comparing Vitest vs Jest

not sure how interesting to others, but i thought this was really cool.

(I am not affiliated with posthog at all. Just typed an incorrect address and came across it.)

Has anyone got any good resources for something like this? I haven't touched C in years, and never worked on anything game-like. But it does look like a really interesting project to start something like this.

tldr - `tsc` can be replaced with `tsgo`. `eslint` replaced by `oxlint`, and `prettier` replaced with `oxfmt

this makes me want to play simcity again! really cool

just saw this today - "whenwords, a relative time formatting library that contains no code." I wonder with AI this will become a popular thing soon that we see other 'libraries' doing... provide good specs, leave it to AI (And trust ai) to interpret

ah i didn't see those. cool.

If GH has an issue, it seems to always be around 4pm or 5pm GMT. I'm starting to think that i should avoid any planned production releases around this time.

https://howtotestfrontend.com/blog Mostly blog posts about testing react apps, latest news about FE testing, Vitest / Jest etc.

while this approach is useful, i think the diff is too small to catch a lot of bugs.

i use https://www.coderabbit.ai/ and it tends to be aware of files that aren't in the diff, and definitely can see the rest of the file your are editing (not just the lines in the diff)

(not my site, just found it online - seems to be most popular/useful ask hn threads)

Writing articles about how to test frontend apps (mostly react based apps) at https://howtotestfrontend.com/ Adding some final bits to some new vitest browser mode content this week hopefully.

I find the jetbrains IDEs (like Webstorm) has the best UI interface for this. Selectively commit specific lines from your changes.

Wow, imagine this 10 years ago. It would never have been an option.

(Maybe WB acquiring Netflix...)

Same, it is a question of time.

For me, weekends only... I used to do a lot of freelance work (years ago...more than a decade ago), somehow I used to find more time then for side projects... with full time employment is is impossible to find the time.

This sort of older tech always amazes me. Also how insanely expensive ("or around $30.000 in 2025 money") it cost

This is my guide on what Vitest Browser Mode is. It includes configuration/setup guide, example code, and a link to a demo repo with a working version https://github.com/howToTestFrontend/vitest-browser-mode-sta...

Vite. Vitest. Storybook. React.

I wonder how many of these vibe coding build apps will grow to massive apps/be really popular (I imagine a lot of them will)... and what kind of security vulns we'll see everywhere because of how it was initally built...

i can only imagine that services like described in this article will become a very common part of getting proof of concepts built with AI into production.....

I wonder what it will be like in 5-10 years time to look back at this sort of time, as we start to figure out the next way to code...