Don't forget that JS is often in a UI, doing asynchronous event/IO handling, so testing timing is important, not just spelling. (great, that's exactly the property names that object would have had, if it existed yet)
That, and it's often reading in data (JSON or XML) from another system, and it is what it is, so see if it quacks or not.
From the people that brought you SOAP, it's (drum roll) TYPE SCRIPT!
It's not really solving my problems, just making more work.
So because Microsoft made SOAP and also made TypeScript then TypeScript must be bad? That's nonsense.
Also, I'm not a frontend guy, and the comment I was replying to was talking about node.js, but having to put a setTimeout or something in your tests just seems wrong.
re: timeout. Yeah, waiting for one (or many!) other async operation(s) to complete in response to an event is a nuisance, but that's how it works, in particular if you don't want a UI to freeze up.
Full stack is hard, at least if somebody wants you to swap in and out of levels several times a week. But that's another rant about ruining projects...
That, and it's often reading in data (JSON or XML) from another system, and it is what it is, so see if it quacks or not.
From the people that brought you SOAP, it's (drum roll) TYPE SCRIPT!
It's not really solving my problems, just making more work.