Dealing with 500 collection Error whereas working Jmeter Selenium script in Azure pipeline

1. Utilizing Selenium for efficiency testing is not beneficial by Selenium builders

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

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

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

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

1. The browser (i.e. Firefox or Chrome)
2. The related model of WebDriver (i.e. Geckodriver or Chromedriver)
3. Be certain 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 below tremendous consumer account it’s good to cross --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 below check perspective, useful resource footprint might be a lot decrease and it is possible for you to to gather extra complete check outcomes and metrics.