I know Selenium is often leveraged for integration testing in mid-to-large-sized companies, and you can use the specific browser drivers to execute on.
For companies not capable of spinning up or supporting their own testing infrastructure, you can leverage BrowserStack.
Something like Protractor.js and Browserstack could provide the type of support needed. It could be cost prohibitive based on testing requirements.
we use Selenium for cross browser testing (including mobile devices). But it is often quite a pain, since the naive idea that "same API" (Webdriver) means that a test case runs equally well on all browsers is simply not true.
You need to tailor test cases a lot to make them run stable on more than one browser/device, which is a lot of work and makes it hard to keep test code clean.
I wrote a bit about that down here: The Selenium Bliss and Pain.
What helps a lot is to have a good testing framework around Selenium. For instance I like a lot Codeception. With a framework like this you can arrange your test code in a way which suits your cross-browser needs.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To add a little here:
I know Selenium is often leveraged for integration testing in mid-to-large-sized companies, and you can use the specific browser drivers to execute on.
For companies not capable of spinning up or supporting their own testing infrastructure, you can leverage BrowserStack.
Something like Protractor.js and Browserstack could provide the type of support needed. It could be cost prohibitive based on testing requirements.
Hi Ryan,
we use Selenium for cross browser testing (including mobile devices). But it is often quite a pain, since the naive idea that "same API" (Webdriver) means that a test case runs equally well on all browsers is simply not true.
You need to tailor test cases a lot to make them run stable on more than one browser/device, which is a lot of work and makes it hard to keep test code clean.
I wrote a bit about that down here: The Selenium Bliss and Pain.
What helps a lot is to have a good testing framework around Selenium. For instance I like a lot Codeception. With a framework like this you can arrange your test code in a way which suits your cross-browser needs.