Going through 500 sequence Error whereas working Jmeter Selenium script in Azure pipeline

1. Utilizing Selenium for efficiency testing is not really helpful by Selenium builders

   Efficiency testing utilizing Selenium and WebDriver is mostly not suggested. Not as a result of it’s incapable, however as a result of it isn’t optimised for the job and you’re unlikely to get good outcomes.

2. Utilizing Selenium for efficiency testing is not really helpful by WebDriver Sampler builders

   Word: It’s NOT the intention of this undertaking to switch the HTTP Samplers included in JMeter. Slightly it’s meant to go with them by measuring the tip consumer load time.

In case you actually must conduct browser-based efficiency testing ensure to put in:

1. The browser (i.e. Firefox or Chrome)
2. The related model of WebDriver (i.e. Geckodriver or Chromedriver)
3. Make sure that to configure the WebDriver to run in headless mode
4. Comply with webdriver and working system documentation, i.e. for those who’re working Chromedriver beneath tremendous consumer account you want to move --no-sandbox command-line argument

For additional help please share request and response particulars from View Outcomes Tree listener, your JMeter configuration and jmeter.log file

Nevertheless it is higher to make use of JMeter’s HTTP Request samplers, given you configure JMeter to behave like an actual browser there needs to be no distinction in any respect from the system beneath take a look at perspective, useful resource footprint can be a lot decrease and it is possible for you to to gather extra complete take a look at outcomes and metrics.