Test configuration object ignored for viewportHeight and viewportWidth

[maximilianschmid]

Current behavior:

Testrunner browser window does not respect viewportWidth and viewportHeight configuration passed in via a configuration object to the test or suite function as the second argument.

Your test checks if config object get's the value, which it does.
4cfcae2#diff-8a1bc60bd20378ff06f1cd550ab21defR59

But the testrunner browser window does not get resized.

Desired behavior:

Testrunner browser window should respect viewportWidth and viewportHeight passed in via a configuration object to the test or suite function as the second argument.

Test code to reproduce

describe('demo.planfred.com …', {
  viewportHeight: 800,
  viewportWidth: 400,
  baseUrl: 'https://demo.planfred.com/'
}, () => {
  it('test', () => {
    cy
      .visit('https://demo.planfred.com/')
  })
})

Versions

4.8.0

Should work in 4.8.0 according to feature issue #7167

[jennifer-shehane]

Yes, I can confirm setting viewportHeight and viewportWidth is not actually changing the viewport size of the suite/test that it's passed to in 4.8.0.

The original PR is only checking that the Cypress.config().viewportHeight, etc values are correct, but there have been other instances where this value can be correct and actually have no effect on the behavior of the test.

The baseUrl is taking effect and working in the example below however.

describe('test', {
  viewportHeight: 200,
  viewportWidth: 400,
  baseUrl: 'https://example.cypress.io'
}, () => {
  it('test', () => {
    cy.visit('/').then(() => {
      expect(Cypress.config().viewportHeight).eq(200) // passes
      expect(Cypress.config().viewportWidth).eq(400)  // passes
    })
  })
})

[cypress-bot]

The code for this is done in cypress-io/cypress#8006, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 4.11.0.

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