Closed nuttmeister closed 6 years ago
I think the proposal is good, particularly item 2. If it's outside the scope of the original project, you could have it be an enhanced fork.
Just like wrk2 is an improvement over wrk.
Sounds interesting or is it outside the scope of the intention of the program. If so, then let me know :)
This is quite outside the scope of Vegeta which was originally to load test HTTP services and APIs, not complex web applications user flows.
We are looking into using Vegeta not just as a load test, but for testing uptime and a bit more complex load tests such as making purchases that needs specific cookies and headers to be set based on a previous request.
I'm looking into making the necessary changes now and if you want you will get an pull request on it.
So in our case I'm thinking of implementing:
Sounds interesting or is it outside the scope of the intention of the program. If so, then let me know :)
But was thinking of having it be able to run more advanced load tests that depends on results on other queries. But also as a drop in replacement for say, Pingdom. Being able to run "Uptime/Transaction" on sites for example, even running as a lambda function on aws.