https://cypress.io logo
Join Discord
Powered by
# help
  • e
    To make things more confusing, I have a console log to confirm it's being run but cypress isn't picking up on that
  • e
    I'm beginning to think this has to with how I'm testing. It might be the case that 
    cy.spy
    is only meant to be used after directly invoking a function that calls it. But what I want to test is that after a particular series of user interactions the method was called
  • e
    I just called it manually and the test passes, so I think that is the case and this would explain why the documentation shows calling a method before asking Cypress whether another function was called
  • h
    @User @User i tested using Vite as the dev server and it works as expected. So Webpack seems to be the culprit. I also tried with a stripped down webpack config and no luck there.
  • b
    Finally getting back on it @User it will probably be one of the plugins. give me a few minutes to get my hands on the culprit
  • h
    Thank you! I really appreciate it 🙂
  • b
    at a glance I have had trouble with this plugin 
    ReactRefreshWebpackPlugin()
    since we do not use HMR as we re-run all the tests in the file when code changes
  • h
    I also tried with this webpack config and it was still unable to find any tests in the file:
    Copy code
    const path = require('path');

module.exports = {
  mode: 'development',
  devtool: false,
  resolve: {
    extensions: ['.js', '.jsx', '.tsx', '.ts', '.scss'],
    alias: {
      '@': path.resolve(__dirname, '..', 'src'),
    },
  },
  module: {
    rules: [
      {
        test: /\.tsx?$/,
        exclude: [/node_modules/],
        use: [
          {
            loader: 'ts-loader',
            options: {
              transpileOnly: true,
            },
          },
        ],
      },
    ],
  },
};
  • b
    The problem is not your webpack config
  • b
    ... there is a bug in cypress CT
  • b
    hum
  • b
    that is embarrassing
  • h
    part of the game!
  • b
    it is alpha software
  • b
    When we do not return config in the plugins/index.js file
  • b
    this exact thing happens
  • b
    Could you create an issue to track it
  • b
    ?
  • h
    sure!
  • b
    and in the meant time, unlock yourself by adding 
    return config
    after this line: https://github.com/andrew-anguiano/reproductions/blob/main/cypress-component-testing-16784/cypress/plugins/index.js#L26
  • b
    Now it works
  • b
    ...
  • b
    Well, it works if you remove the react refresh plugin
  • b
    in CT
  • h
    Ah ok, I'll try that.
  • b
    I could make a quick PR too
  • h
    I think i have it working in the repro repo now following that advice. Although it's showing me this error for the test which could be a config issue on my end.
  • b
  • b
    you forgot one part of the removing react refresh 😉
  • h
    thanks for the pr! and the help 🙂
1...212223...252Latest