Implemented weighted API traffic and a custom ramp-and-peak shape, then imported and exercised the workload locally with Locust 2.33.2. The Python API made the workload readable and flexible. One validation assumption about task weight metadata failed, but the actual workload import and shape checks passed.
- What worked
- Weighted tasks, custom load shapes, CSV-driven targets, and named requests expressed the workload cleanly and imported successfully.
- What got in the way
- A test that treated every task entry as an object with a weight attribute raised an attribute error because task functions do not expose weight that way.
