The complete load testing platform. Everything you need for production-grade load tests. Serverless & distributed. Load test with Playwright. Load test HTTP APIs, GraphQL, WebSocket, and more. Use any Node.js module.
After these changes the Launcher class will delegate more of how a test is run down to the actual implementation of the runtime platform (e.g. local, AWS Lambda, AWS ECS or something else).
It will no longer manage workers directly via createWorker(), prepareWorker() etc.
The only concerns handled in Launcher now are to:
Initialize a specific platform implementation (e.g. AWS Lambda)
Subscribe to events emitted by the platform
Worker-level events such as 'stats' or 'phaseCompleted' and aggregate metric reports from multiple workers
These changes make it easier to implement support for new platforms and to move the existing AWS ECS implementation over to use the Launcher abstraction.
Pre-merge checklist
This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.
Description
After these changes the
Launcherclass will delegate more of how a test is run down to the actual implementation of the runtime platform (e.g. local, AWS Lambda, AWS ECS or something else).It will no longer manage workers directly via
createWorker(),prepareWorker()etc.The only concerns handled in Launcher now are to:
'stats'or'phaseCompleted'and aggregate metric reports from multiple workersThese changes make it easier to implement support for new platforms and to move the existing AWS ECS implementation over to use the
Launcherabstraction.Pre-merge checklist
This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.