New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Component testing does not honour configuration values provided by plugins. #16424
Comments
Seems like a regression. Those defaults should be applied to both e2e and CT. Are you launching the component testing runner using |
I was not able to reproduce this. I'm using the Component Testing runner with the latest version of Cypress (7.3.0). My overrides in I could be misunderstanding your issue. Maybe you can clarify, or post an repository I could pull down and run? Another thing that might be of interest is you can get the test runner (either e2e or component) from the module.exports = (on, config) => {
if (config.testingType === 'component') {
// something component testing specific, return modified config?
}
if (config.testingType === 'e2e') {
// something e2e specific, return modified config?
}
return config
}
|
I'm not talking about the viewport props, or any other configuration value, I'm talking purely about the logic that is used to find the component spec files. When I run my test suite with purely configuration values provided by the plugin which sets the While the console output does correctly state that a spec file has been found:
|
In your above screenshot, it looks like the sidebar is just really small. See this comment. Back to your issue: I understand now and I reproduced the problem by creating an empty |
I am working on this here. I added a minimal reproduction. |
Ok, I fixed it: #16468 |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
In Cypress
^6.8.0
it was possible to configure component testing using a plugin file by modifying the received configuration. Since the release of 7 this is no longer possible and requires you to configure component testingin the
cypress.json
file instead.Desired behavior
It should honour the plugin overrides.
Test code to reproduce
The Cypress.json that is now required, (this was empty on 6.8.0)
The previous configuration merged in a plugin file:
Packages:
-
cypress
: ^7.2.0-
@cypress/react
: ^5.4.2-
@cypress/webpack-dev-server
: ^1.1.6Environment:
-Node.js: v12.9.0
-NPM: 6.10.2
The text was updated successfully, but these errors were encountered: