Right here is the AUT workflow throughout environments:
Code strikes (and will get secure) from dev > QA > Stage > Prod
Information strikes (and will get dirtied) from Prod > Stage > QA > dev
We’ve got Efficiency Check scripts in LoadRunner (or JMeter) together with Jenkins with the corresponding plugins (HPE Automation Instruments and Efficiency plugin for Jmeter) configured to run in opposition to Stage each time a new construct is deployed to Stage.
The run nearly all the time fails because of the truth that scripts would wish to get up to date for: Entrance finish modifications & Information modifications.
At this level, we repair the scripts instantly and run the check, publish the outcomes – all manually. We really feel this defeats the aim of getting the pipeline in place.
I’m pondering of an answer during which we are able to replace the scripts based mostly on QA (as soon as the construct is deployed right here earlier than it will get deployed to stage) after which replace the scripts once more by operating it in opposition to Prod (fastidiously, in fact) for knowledge updates after which set it as much as be triggered by Stage Job at Jenkins finish. This looks like a really cumbersome course of.
My query is – are there any various options to this? Do you see issues (aside from touching Prod, which not often occurs in actuality) on this method?
How do you deal with CI/CD/CT Utilizing Jenkins (we are able to additionally use IBM uDeploy/urbancode as effectively) and LoadRunner/JMeter in a multi-environment scenario like above? Are there any Greatest Practices documentation on the market which we are able to discuss with?
