re: What dev topic do you think you should understand, but don't? VIEW POST


The timeline for when this needs to be done is Tuesday, apparently, to prioritize performance fixes. And they already barely approve of me reading my JMeter book.

And even though it literally has "testing" in the name, the project manager is making the devs do the automated testing of it. Maybe so the "real" engineers will do it right? Whatever. But when shit breaks, I suddenly need to drop all the real work and manually click things for a week.

What's the easiest thing to do that can give you some value? Going through the whole JMeter book is going to take time.

What about employing a third party load testing tool or a tool like wrk to have a baseline of a few endpoints?

Maybe you can also use Cypress to record those use cases you usually do manually...

code of conduct - report abuse