We currently use Protractor + LambdaTest + Jenkins to execute our test scripts across all major browsers, including Safari, and on real mobile devices.
With Protractor deprecated since the end of 2022, we are planning to migrate our existing automation suite to Cypress.
Before proceeding, we want to confirm: can Cypress, when integrated with LambdaTest, support test execution on the Safari browser and mobile devices (iOS and Android)?
Our goal is to maintain the same cross-browser and mobile test coverage after migration, eventually running the stack as Cypress + LambdaTest + Jenkins.
Can someone confirm if this setup supports Safari and mobile testing with Cypress?
Any suggestions or limitations would be appreciated.
We made a similar transition from Protractor to Cypress earlier this year, and I can confirm that LambdaTest supports Cypress execution in their cloud grid, but with a caveat: Safari and real mobile devices aren’t supported directly for Cypress tests yet.
Cypress runs inside a Chrome-based browser engine, so for mobile or Safari-specific validation, what we did was simulate mobile viewports in Cypress using cy.viewport() for responsive layout checks.
But for true device/browser validation (like iOS Safari), we still rely on traditional Selenium-based tests.
We now run a hybrid setup: Cypress + LambdaTest for fast, consistent desktop testing, and use Playwright or Selenium for the few critical flows that absolutely need real mobile/Safari validation.
Hope that helps!
Just went through this exact decision point at my org. While LambdaTest has amazing integration with Cypress, including parallel test execution and CI pipelines, Cypress itself doesn’t support Safari or real mobile browsers natively, that’s a limitation on the Cypress side, not LambdaTest.
Our workaround? We migrated most of our regression tests to Cypress for speed and reliability, but kept a small suite in Selenium for mobile and Safari cross-checks.
That way, we didn’t lose coverage while still gaining Cypress’s developer-friendly features.
LambdaTest handled both frameworks really well, so Jenkins just calls both test sets in sequence. If full mobile + Safari coverage is a must, I’d recommend this dual-framework approach.
tthe exact same stack (Protractor + LambdaTest + Jenkins) and faced this during our migration too.
The short answer is: Cypress can be integrated with LambdaTest, but it’s limited to Chromium-based browsers.
That means no native Safari or real device testing via Cypress for now.
What we did to bridge this gap was use LambdaTest Screenshot and Smart UI testing for Safari and mobile devices. We trigger those from Jenkins after the Cypress run to visually validate layouts.
It’s not perfect for full E2E logic, but it helps catch Safari-specific issues.
Also, worth keeping an eye on updates, LambdaTest is expanding Cypress support constantly, so things might change soon.
Just make sure to plan around Cypress’s inherent browser limitations.