Comment by markalby

In web dev, writing load tests and user journey scripts has become a lot easier and something where the end result is more important than the code flavor, compared to maintainable site feature code.

Turn on persist logs in the dev tools network tab; go through as much as the flow as possible; filter out domains that aren’t your site: google, facebook, external api calls; download the .har for all of whats left; convert har into a k6 script using a library, or dump that into an llm to convert it to their newer browser script and point the llm at their docs; edit it to be dynamic so you can test paths from different product pages/types, and scrape and enter proper guids, etc.

On the flip side we’re seeing a lot more bot traffic likely due to bad actors doing this too, but by writing these tests you begin to see what calls cause load and be proactive.