Expose configuration through module API

[badeball]

What would you like?

As a preprocessor-maintainer, I would like to have configuration resolvement exposed through the module API, like shown below.

const cypress = require("cypress");

await cypress.resolveConfiguration(["--config", "numTestsKeptInMemory=10"], process.env);

/**
 * => {
 *  baseUrl: null,
 *  numTestsKeptInMemory: 10,
 *  integrationFolder: "cypress/integration",
 *   
 *   ...
 * 
 * }
 */

Why is this needed?

To make stuff like this more water-tight. We can only attempt to re-implement the resolvement process, but it's obviously always going to be flaky, unrobust and surprising to the end-user.

[badeball]

Even better would be to be able to resolve the actual files to be run. Having the configuration is a step in the right direction, but I realize now we would actually still have to re-implement the pattern matching and handling of ignoreTestFiles.

[jennifer-shehane]

Thanks for taking the time to explain the feature you'd like.

Our team has decided that adding this feature is not currently within the scope of feature work that our team is planning to work on.

This would actually take quite a bit of effort to get working, for a small use case that already has a workaround.

We would be open to reviewing any Pull Requests made implementing the feature. We will also reconsider picking this back up if we see this issue gains more 👍 or comments in support.

[badeball]

In case anyone stumbles upon this - I've created https://github.com/badeball/cypress-configuration which does re-implement this. FYI, I'm fine with maintaining this myself, but of course wouldn't mind if this ever does get exposed.