Open dschweie opened 9 months ago
Hi Dirk,
Thanks for the Enhancement request,
There are two ways I can see to potentially implement this
There are pros and cons to both, option 2 would be a breaking change (something I try to avoid) but also would be neater and more maintainable in the long run (something I strive for)
Happy to hear thoughs on these options or if you have a another suggestion on how to impliment it
When I start a performance test campaign I have to plan scripting phase. It is my expectation that I can reuse the test cases written bei Technical Test Engineers and pick them just by configuration. The process to get a copy of test cases and adding thinktimes and pacing is not so nice. If I think about a second campaign, I do not want to update my copied selection
The performance test should be written like a configuration file. The configuration file should reflect a hierarchy so I would prefer YAML. This is text based format which is famous to most engineers in software branch.
This feature will reduce the time to first test execution and the effort to maintain test scripts is mostly given to those Test Engineers who are familiar with the SUT. Maybe we also make performance testing more often happen.
NeoLoad As Code might be a pretty nice solution where you might get ideas from.