https://cypress.io logo
Join DiscordCommunities
Powered by
# general-chat
  • w
  • w
    OH, it's only when I click in navigation, that's interesting
  • w
    direct links work.
  • b
    @User this sounds like a Nuxt quirk
  • w
    https://docs.cypress.io/guides/overview/why-cypress - I click on Guides -> Command line
  • w
    404
  • u
    I'll check it out, thanks
  • r
    Hi, Iā€™m doing cypress code coverage for nuxt. I implemented Istanbul and nyc but is still missing something
  • r
    Some of you can recommend me a guide?
  • b
    That is possible indeed, could we move this convo to #755921440359841852 or #755913900024791046 ?
  • f
    Whoops, I assumed this was for general Cypress questions. I'll repost it over there.
  • a
    Hey guys. Not sure the best channel for this question, so if I need to move it, just let me know. I have an application built using NextJs, and I am trying to now set up Github Actions for Cypress. It's running, but the only test case that passes is the test that involves the login page. Any test beyond logging in fails, and I assume this is because the application is never making it past the login page when running. My way to do this when running the tests locally is to set an env variable of IS_TEST_MODE = true, which logs the user in with a hardcoded UN and PW instead of Okta 2FA. Since I am new to both Github Actions an Cypress, I am not confident where I am going wrong.
  • b
    this indeed looks like an e2e question for #755913900024791046 šŸ˜‰
  • a
    okay ill move it over there! thanks!
  • m
    Hello all šŸ™‚
  • m
    How are you handling your tsconfig when using cypress in VSCode ? We use --isolatedModules in our main tsconfig but most e2e cypress tests doesn't import/export things so TS isn't really happy
  • m
    Our workaround is to export an empty object
  • m
    I know I can make a dedicated tsconfig for cypress, but then the issue will be that vscode will still pick our main tsconfig.json for its feedback
  • m
    as we collocate the tests with the components/screens under test we can't apply two tsconfigs šŸ˜…
  • f
    I followed a lot of guides that also added the 
    tsconfig
    inside of cypress. In the beginning I was doing some includes and then going one level up - it was not working. Then I just tried to drop it from the cypress folder and it worked just fine
  • f
    Copy code
    json
{
  "compilerOptions": {
    "target": "es5",
    "downlevelIteration": true,
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "baseUrl": ".",
    "paths": {
      "~/*": ["*"]
    },
    "types": [
      "cypress",
      "@testing-library/cypress",
      "cypress-localstorage-commands",
      "cypress-plugin-stripe-elements"
    ]
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules"]
}
  • f
    in my root folder
  • f
    cypress.json
    Copy code
    json
{
  "baseUrl": "http://localhost:3000",
  "viewportWidth": 1000,
  "viewportHeight": 660,
  "integrationFolder": "cypress/tests",
  "component": {
    "testFiles": "!(node_modules|cypress)/**/*.spec.{js,ts,jsx,tsx}",
    "componentFolder": "./"
  },
  "chromeWebSecurity": false,
  "experimentalStudio": true,
  "$schema": "https://on.cypress.io/cypress.schema.json"
}
  • f
    this setup allows me to run both normal cypress and component testing cypress with typescript
  • m
    @User Isn't VSCode complaining when you open a spec file?
  • m
    As it relies on your root tsconfig.json to do TS background type checking on the opened file?
  • m
    I understand it works at the CLI level, but in my case it gives me false positive in VScode :p
  • f
    What type of complaining are you seeing?
  • m
    In e2e tests we don't necessarely import/export things
  • m
    so with isolatedModules: true in the tsconfig it complains
1...789...127Latest