Dynamically setting baseUrl with TestConfigOverrides

[PepijnSenders]

Current behavior

In v9 we were able to set the baseUrl but it has disappeared from the TestConfigOverrides type.

Desired behavior

Add the e2e key to the TestConfigOverrides type.

Test code to reproduce

cypress/cli/types/cypress.d.ts

Line 3006 in e6b2466

interface TestConfigOverrides extends Partial<Pick<ConfigOptions, 'animationDistanceThreshold' | 'blockHosts' | 'defaultCommandTimeout' | 'env' | 'execTimeout' | 'includeShadowDom' | 'numTestsKeptInMemory' | 'pageLoadTimeout' | 'redirectionLimit' | 'requestTimeout' | 'responseTimeout' | 'retries' | 'screenshotOnRunFailure' | 'slowTestThreshold' | 'scrollBehavior' | 'taskTimeout' | 'viewportHeight' | 'viewportWidth' | 'waitForAnimations' | 'experimentalSessionAndOrigin'>> {

Cypress Version

10.0.2

Other

No response

[mschile]

The baseUrl option was removed with #20589. However, it is still listed as a test configuration option in the docs.

Setting the baseUrl at the root succeeds:

  it('should visit', { baseUrl: 'http://127.0.0.1:8080' }, () => {
    cy.visit('/')
  })

However, setting baseUrl within e2e fails:

  it('should visit', { e2e: { baseUrl: 'http://127.0.0.1:8080' }}, () => {
    cy.visit('/')
  })

@estrada9166, do you know if we are intending to support baseUrl at the root level or within e2e for the per-test configuration?

[jennifer-shehane]

We want to support setting baseUrl at the root level in the testConfigOverrides, as we always know at this point which testing type we're in.

[PepijnSenders]

@jennifer-shehane @mschile what's the status on this? We still need to add baseUrl to the type.

[mschile]

@PepijnSenders, there is a PR open to fix this issue #22445. Once that PR merges it will go in the next release.

[cypress-bot]

Released in 10.3.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v10.3.0, please open a new issue.