https://cypress.io logo
Join Discord
Powered by
# help
  • b
    Anyone have this error show up when running Cypress locally with 
    npx cypress run
    ? I can run my tests fine one by one with 
    open
    and on CI, but running it locally it'll give me that error after running each file. `"after all" hook: generateReport for "is not interactive": CypressError: 
    cy.task('coverageReport')
    failed with the following error: > Cannot read property 'loc' of undefined Because this error occurred during a 
    after all
    hook we are skipping all of the remaining tests.`
  • b
    it looks like a code coverage issue
  • b
    and the "loc" thing is usually linked to items on a babel Abstract Syntax Tree
  • b
    So @User did you instrument your code in your babel config? In other words did you add anything istabul related in the babel config that you are using for cypress?
  • b
    thanks for the reply! I'm currently instrumenting with the babel plugin like so
    Copy code
    javascript
if (process.env.NODE_ENV === 'test') {
  plugins.push([
    'babel-plugin-istanbul', {
      extension: ['.js', '.vue'],
      exclude: ['**/*.stories.js'],
    },
  ]);
}
  • b
    lemme check that the code is actually getting instrumented
  • b
    yeah it seems like all files are instrumented under the 
    window._coverage
    object
  • b
    could there be a version mismatch between the plugin and waht cypress asks for?
  • b
    I found this example that could help debug it https://github.com/bahmutov/code-coverage-vue-example
  • b
    sweet, will take a look later 🙂 thanks!!
  • p
    **Opinions Wanted: **We have a highly animated (gsap+webgl) long scroll site we are wanting to setup automated image diffs for. We have devised a way to put animation "label" and specific scroll heights (responsive) and we're thinking of storing these in a global on 
    window.$anim_steps
    and then just having cypress iterate through those taking snapshots. Can anyone think of a better way to make this list of steps available to cypress other than window object that is fancier/cleaner? LocalStorage? other?
  • r
    Would I need to instrument my code if I was going to try to get code coverage on an external url ?
  • r
    thanks!
  • b
    I do not think you can get coverage on an external url
  • b
    since you do not "own" the code
  • b
    What coverage would you expect to get?
  • b
    And how would you hope to use the coverage?
  • r
    @User I was trying to run cypress code coverage against a Gatsby site in a GitHub action but since the site takes 45 minutes to get the dev server running from a cold start I was trying to use Gatsby Cloud build that build in a few minutes for the CI test. I can't get the dev server up fast enough before everything times out. Does that make sense ? Thanks!
  • r
    I do own the code
  • r
    @User Its just not working for the CI cause it needs to download all the images
  • r
    In theory if I could get it run the dev server once I could store the cache folder but I can't get it to work once hahaa
  • r
    Any advice would be great
  • r
    I was thinking about using https://github.com/JS-DevTools/coverage-istanbul-loader/blob/master/examples/hello-world/webpack.config.js to maybe instrument the code in a specific build situation maybe that could work
  • r
    @User The coverage I guess would be artifact for that PR that says the code had this amount of coverage at that particular time
  • b
    The way istanbul works is: - it adds signals in the code (instrumentation) - records these signals while running the tests - use sourcemaps to re link the recorded paths with the actual code (report)
  • r
    However I guess I could make sure that works locally and then I know if the tests pass than I am good to go
  • b
    Can you add instrumentation with Gatsby Cloud
  • b
    ?
  • r
    Ok then maybe the webpack plugin could work
  • r
    Gatsby cloud is just the build tool but I could add it to webpack
1...789...252Latest