https://cypress.io logo
Join DiscordCommunities
Powered by
# general-chat
  • u
    what should I even be looking for thats causing the tests to jsut repeat over and over and over again?
  • f
    @User did you mean to share something else, or are you referring to your past posts?
  • u
    Well unsure what to share
  • u
    They ran in a loop for 4.5hrs
  • u
    That's a lot of debugger code lol
  • u
    I ended up wiping cypress then reinstalling it and tgat seemed to fix the issue. The cache had gotten way to large
  • u
    Copy code
    2021-04-28T23:50:56.8209037Z ##[section]Starting: Run e2e Tests
2021-04-28T23:50:56.8427976Z ==============================================================================
2021-04-28T23:50:56.8428386Z Task         : Command line
2021-04-28T23:50:56.8428732Z Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
2021-04-28T23:50:56.8429051Z Version      : 2.182.0
2021-04-28T23:50:56.8429311Z Author       : Microsoft Corporation
2021-04-28T23:50:56.8429696Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
2021-04-28T23:50:56.8430125Z ==============================================================================
2021-04-28T23:50:58.2687046Z Generating script.
2021-04-28T23:50:58.2789311Z Script contents:
2021-04-28T23:50:58.2796521Z cd "C:\agent2\_work\r2\a\tests" && npx cypress@6.2.0 run --browser chrome --headless --spec src\Tests\integration\alphaledger\build-verification\GSHP\gshp.spec.js --config baseUrl=https://org.dev.alphaledger.com
2021-04-28T23:50:58.3221178Z ========================== Starting Command Output ===========================
2021-04-28T23:50:58.3444134Z ##[command]"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\agent2\_work\_temp\07a08bd5-42f5-4bb6-ae84-8f8f7e70491b.cmd""
2021-04-28T23:51:43.5665883Z npm ERR! code ELIFECYCLE
2021-04-28T23:51:43.5688189Z npm ERR! errno 1
2021-04-28T23:51:43.5689053Z npm ERR! cypress@6.2.0 postinstall: `node index.js --exec install`
2021-04-28T23:51:43.5689683Z npm ERR! Exit status 1
2021-04-28T23:51:43.5690122Z npm ERR! 
2021-04-28T23:51:43.5690622Z npm ERR! Failed at the cypress@6.2.0 postinstall script.
2021-04-28T23:51:43.5691319Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  • u
    though I am receiving this issue. this was an issue stopping my build pipeline. so i uninstalled and removed cypress from the repo and installed it globally on the VM. i then did the same commands I run in azure devops and it worked great but then when the release tries to execute this i get this error. I am unsure why this is an issue. Cypress currently lives on the user/appdata/local/cypress/6.2.0
  • u
    Hey everyone, i'm looking for a tool to specifically aid us in automated live testing and was wondering if anyone has used cypress in this way. What I'm looking for is when changes have been done and released to production, I would like to run lets say 5 smoke tests covering key user flows i.e login -> click menu button, login -> go to this url.
  • b
    Hello @User this seems like a perfect use case for cypress indeed. You can use a 
    baseUrl
    and do google stuff if you want. I know people found a way to automate cypress to buy them a PlayStation 5
  • w
    I have done this in the past with a really complicated form. In my case we didn’t really have a CI pipeline that could run these against production because there was a caching layer that we didn’t control & the timing could be a bit unpredictable. So what I’d do once cache was cleared after deployments, and folks were starting to validate the live site, was just run the cypress tests from my command line. That test suite would also send sample payloads to prod endpoints and make sure that, eg, a contact form submitted to our backend would get back a response including a salesforce ID, stuff like that. It was helpful.
  • u
    I have cypress globally installed. is there anyway to still get intellisense on the tests?
  • s
    Triple equals typedefs, I think...
    Copy code
    /// <reference types="cypress" />
  • s
    @User
  • u
    But when installed in the repo this wasn't an issue but I'll give it a go
  • g
    Unfortunately I could not find a way to do this in VSCode
  • u
    Hello folks - apologize if this is the wrong place to ask questions.I am trying to try out Cypress for my company and am running into proxy / firewall issues. I was able to get past the point where it was not downloading at all. But now the page load times out. I assume it's related to the proxy setup. Our company is kind of silo'd and networking and security teams are very particular about opening internet access from internal systems. I'm not a networking guy but is there someone that can help with getting it setup? Would really appreciate any help
  • s
    Hey @User I think this is best posted in #763105090679865354
  • a
    Hi all, I am trying to use Cypress code coverage for my react app. I am able to instrument the code when run locally and its generating coverage reports as expected. Now I am trying to find a way to instrument the code for the beta app being deployed in the AWS CodePipeline so that I can run code coverage on it as well. How can I instrument the code for this beta stage app ? If I go to console and check for window.__coverage___ . It returns undefined which tells me that the code isn't instrumented. Any leads would be appreciated! @User Can you help me out here....? Just wanted to know how can I instrument the app that will be deployed in my pipeline - like the beta app app here gets deployed in the pipeline. I do have a buildpsec.yml file used to configure the commands that needs to be run in this pipeline. Do I have to add anything here so that the code gets instrumented ?
  • u
    I am running into a few issues with pg and cypress. So I tested the file in jsut a normal js file and ran it with node and it work great. then I converted it to a cypress test and it gives me Module not found: Error: Can't resolve 'pg' in
  • u
    Copy code
    describe("test", () => {
  it("test", () => {
      cy.task("query", {
          sql: `select * from "user" u where u.first_name = ('Cypress') and u.last_name = ('Issuer')`
          // values: [ "InStock", 40 ]
      }).then(res => {
        expect(res.rows.length).to.be.greaterThan(0)
      })

      // your cy assertions here
  });
});
  • u
    Copy code
    module.exports = (on) => {
    on('task', {
        query ({sql, values}){
            return client.query(sql, values)
        }
    })
}
  • u
    just odd this error only happens when cypress runs but when i use node to run the file it works no problem
  • u
    Copy code
    const { Client } = require('pg')
const client = new Client({
  user: '',
  host: '',
  database: '',
  password: '',
  port: ,
})
client.connect()
  • a
    HI all...Can anyone help me with this scenario ?
  • s
    Hi, I've just upgraded to Cypress 7.3.0, looks awesome! I also use the 'included' docker image on Jenkins. However, it looks like the PR for the 'included 7.3.0' is ready to go but for some reason not merged yet. Anyone know why? 🤨 I'm eager to let Jenkins have a go with the new and shiny version. 🙂 https://github.com/cypress-io/cypress-docker-images/pull/486
  • s
    Never mind, fixed now 🙂
  • l
    Hi, my name is Manuel 👋 . I'm a software engineer currently working on a automation for project for the QA team(and devs) in my organization. Sometimes, I contribute to Cypress on my free time. I'm happy to join this discord! 🙂 I was wondering if we could create a channel for code reviews & open source? Thanks 🙏
  • s
    Hello! 👋
  • s
    Hmm.. we could put it in the e2e or ct channels
1...567...127Latest