Hi I can't run cypress 10 with linux and jenkins ? who can help on this ? got the following issue: Is it a bug ? or there are some instructions should be followed to run cypress-10 on linux | Jenkins ?

yes

has anyone figured out how to query postgres after upgrading to cypress 10? The two libraries i know of cypress-postgres and cypress-postgresql has not been updated and I can no longer access the postgres database. is there a new way to do this?

Does anyone know how to set any of the metadata above testsuite in a junit report generated from the

--reporter junit

runtime option?

Hi all, Can anyone let me know on how to include number of test cases passed and failed in the slack notifications. I have sent the Jenkins build report in slack but the report doesn't have these details. Can anyone please help me on this

Hi did you get the solution? I need help on this

@wonderful-match-15836 @nutritious-restaurant-91514 @rough-monitor-85122 Any insight on this?

@best-flower-17510 No idea, I'm not familiar with any of our integrations. I mostly work on the test runner itself.

Hello everyone! Please, someone could help me? Im having problem with my Login with 2 domains.. My system use keykloak, so, when i put login, password and click, take me to another domain, i try to use origin() but doesnt work..

Hi Everyone, can anyone in help with cypress component testing with aurelia app or guide me to any doc or repo for that please?

Found a solution for anyone searching: 1. Downgrade to version 9 2. Use the wizard to regenerate the files 3. Upgrade to version 10 4. Use the v10 wizard to perform the migration.

Sorry for late response, value of the fourth item is the at the second example code. But I want to access what user has written to the input, so I think in that context it is still testing UI?

Hello Is this feature still available in version 10? cypress wait automatically for commands and assertions I upgraded to version 10, all my test suites are failing because of this feature, I think The problem is that the test runner does not correctly wait until the page is loaded Reproduction: 1/ Launch a spec (Success) 2/ Login in an application (Successful) 3/ Login successfully but the page takes a long time to load (Success) (I added 2 retries but the page is still loading) - The test runner continues to execute the following series of tests. 4/ Do a first action (Failure)

Hey! All my test are still waiting the same way as they did before 10.0.0, are you following the action-assertion rule?

Hello @powerful-orange-86819 Tell me more about action-assertion rule

thanks, i'm taking a look now

I understand the concept, I will try it now and come back to you if it works

By

value

i meant, what's the added value of doing so? As you are already stubbing your API, there is nothing special about the input values as you are providing them. By computing data in place of your API, you are trying to see if the API acts the way you expect, that's not about the UI.

value

is just string that's going to be typed in input. > By computing data in place of your API, you are trying to see if the API acts the way you expect, that's not about the UI. I think I have a little grasp of what you are trying to say. However, in my case I would like to make cypress type into the input, for example 'go for walk', and when add todo button is clicked, that's going to shoot the POST API on the server, however I want to intercept request body of this post and dynamically stub my initial GET todo list response. For example it looks like this.

javascript
[
   // Below 3 items are initial stubbed response
  { 
    id: 1,
    name: "Buy milk",
    isCompleted: false,
  },
  { 
    id: 2,
    name: "Run Errand",
    isCompleted: false,
  },
  { 
    id: 3,
    name: "Clean house",
    isCompleted: false,
  },

  // When user clicks add todo button, dynamically add todo item by intercepting POST request. 
  { 
    id: 4,
    name: "go for walk", // this value was typed by cypress
    isCompleted: false,
  }
]

And after this, I want to test my UI if 4th item was added. This is my thought process but please let me know if I am completely misunderstanding the test with cypress.

added value definition (that's not about your form): > an improvement or addition to something that makes it worth more By testing if the item is added, you are testing your own test itself, the one responsible for intercepting data for populating your list. You are testing the data, not the UI.

The success of testing the 4th item is to see it, but what's the failure scenario?

Ah my bad there! Then if stubbed response is displayed correctly in the screen, that is sufficient for UI testing, right? For the mutating 4th item, If I don't need to test 4th item is correctly displayed, I could just check if my request body has been sent correctly without asserting the UI right?

I haven't really considered the failure scenario.

By testing the UI, test as an user: by submitting the form, test you are correctly being redirect to some other page, or having a success message being display, don't test the request itself

Okay that makes sense. Do you have some helpful resources or documentation article about your explanation/philosophy here?

Hello, everyone 🙂 I have Cypress + Cucumber + ts tests and I have updated Cypress version to 10.0.3 today. So, I have some problems with the Step implementation files, them can't be found "Step implementation missing for:..." But everything is configured correctly. Jonas Amundsen in Gitter told me that Cypress 10th version isn't work correctly with the Cucumber + TS tests, is it right? Maybe someone have already updated to 10th version with Cucumber and TS? Thank's for help! Take care of yourself!

https://docs.cypress.io/guides/end-to-end-testing/testing-your-app and

Hello, guys. I'm having an issue with running a test suite inside the container with

cypress/included:10.0.3

image, but it falls appart with

The Test Runner unexpectedly exited via a exit event with signal SIGSEGV

without any explanation. docker-compose looks like this

version: '3'

services:
    cypress:
        image: "cypress/included:10.0.3"
        environment:
            - DEBUG=cypress:*
            - DISPLAY=
        command: "--browser chrome"
        working_dir: /e2e
        volumes:
            - ./:/e2e

The main issue is that even with debug logs I don't understand what is wrong with my setup and why it is failing. And the most interesting part is that it is working fine with

cypress/included:3.3.1

not sure if that's an issue relevant to m1 mac https://github.com/cypress-io/cypress-docker-images/issues/431