reporterOptions are not resolved when they are set in setupNodeEvents

[gustawx]

Current behavior

1. set up reporterOptions in setupNodeEvents
2. start Cypress GUI
3. Go to Settings
4. Go to Project Settings
5. Check Resolved configuration section

results:
reporterOptions are not resolved correctly - like they have been set in setupNodeEvents. They are always set to null. I observed this only fot this one config option.

Desired behavior

reporterOptions resolved correctly, like they have been set in setupNodeEvents

Test code to reproduce

Quite easy to reproduce, just define reporterOptions in cypress.config.ts:

export default defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      config.reporterOptions = {
        reportFilename: "filename",
        html: true,
        json: true,
      };
      // and this only for demo purpose
      config.reporterOptionsAnother = {
        reportFilename: "filename",
        html: true,
        json: true,
      };
      return config;
    },
  },
});

Cypress Version

12.17.2

Node version

18.12.1

Operating System

Windows, Linux, not tested on OS

Debug Logs

No response

Other

No response

[TzolkinB]

Seeing what might be a similar issue. Using Cypress 12.17.1.
We have a global package where we set default configs for repos to consume.

In setUpNodeEvents, console.log(config.reporterOptions) shows the expected default config results but config.resolved.reporterOptions is showing null.

Tested with Cypress 10.7.0 and seeing the same unexpected behavior where config.resolved.reporterOptions is incorrect but config.reporterOptions does show what is expected.

[himkanda]

Able to confirm in my project that this is an issue only with the key-value pair type configurations, like reporterOptions and retries

Cypress version: 13.1.0
Node: 20.5.1
Browser: Chrome 116, Electron 106

Test Code to reproduce:

const { defineConfig } = require("cypress");

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      config.baseUrl = "https://www.google.com";
      config.chromeWebSecurity = false;
      config.defaultCommandTimeout = 35000;
      config.excludeSpecPattern = ["abc.spec.ts", "xyz.spec.ts"];
      config.reporterOptions = {
        charts: true,
        graphs: false,
      };
      config.retries = {
        openMode: 2,
        runMode: 2,
      };
      return config;
    },
  },
});

In cypress settings, I can see that all given config properties got resolved with values provided in setupNodeEvents, except retries and reporterOptions

• retries still shows {runMode: 0, openMode: 0}
• reporterOptions still shows null

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[gustawx]

Hello @jennifer-shehane could someone from Cypress team check this issue? Due to inactivity it will be automatically closed. It's not a good way to handle the issues ;]

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[gustawx]

@jennifer-shehane any update on this issue? Still valid...

[jennifer-shehane]

Has anyone confirmed if this is a bug with the visual display of the reporterOptions/retries in the resolved config in the UI? Or is it also a problem with Cypress reading in these values properly. My guess is that it's a bug in the resolved config VIEW.

[gustawx]

Yes, it really doesn't work, it's not only the UI.