Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Though I'm not an JS expert, I can tell you that runtime issues / issues tearing down E2E tests are pretty valid in any language.
Some testing frameworks just hide it....
Which can lead to funky situations.
I once found out the hard way that a long running CI machine continuously leaked memory thx to this.
Usually a process termination should free up all resources... But the E2E test created a few zombie processes as the main program / e2e test script exited before it's workers / e2e resources were finished....
Took a few months to be noticed.
Took a few weeks to fix the E2E tests properly.... a reboot week kept the memory clean.
I implore ANYONE... please...
Have you EVER written a SINGLE Jest test that didn't have some sort of bullshit spewing stuff like this:
"ReferenceError: You are trying to `import` a file after the Jest environment has been torn down."
"Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports."
and yet running on a device, features work flawlessly and quite well, no errors or even warnings in sight logged
This is the most fragile pile of garbage I have ever seen.
I hate this.
inb4 your stupid ass todo boilerplate garbage you wrote tests for in freshman year. i'm talking about a REAL app with HUNDREDS of components.
where the grownup testing tools at? it's a question I've still not answered after a year of fucking around with this framework
rant
jest
clowndrivendevelopment
clowntown
🤡