fresh-doctor-14925
11/11/2022, 8:48 AMstale-optician-85950
11/11/2022, 9:01 AMnpm cypress info
and see which browsers are detected and if everything looks as you would expect.
https://docs.cypress.io/guides/guides/command-line#cypress-infobetter-ocean-83368
11/11/2022, 2:14 PMfaint-thailand-67863
11/11/2022, 5:07 PMadorable-smartphone-87280
11/11/2022, 5:13 PMfaint-thailand-67863
11/11/2022, 5:19 PMmysterious-belgium-25713
11/11/2022, 7:34 PMstraight-nail-40770
11/11/2022, 10:03 PMbillions-tomato-88210
11/12/2022, 2:06 AMmysterious-belgium-25713
11/12/2022, 8:21 AMgorgeous-musician-66418
11/12/2022, 8:23 AMbillions-tomato-88210
11/12/2022, 3:20 PMproud-gpu-14798
11/12/2022, 3:21 PMcy.intercept
question: I have an app that makes repeated calls to a particular endpoint, what approaches enable a wait for a response body that includes a specific value within the body?proud-gpu-14798
11/12/2022, 3:46 PMcy.intercept
question: I have an app that makes specific API calls to a specific /events/
endpoint, and those requests may be executed in random/different orders, but each definitely has a unique value such as type:"exercise_run_start"
vs type:"exercise_run_end"
I need to validate that all of the expected API calls were executed, and no unexpected API calls to that endpoint where executed (can use a spy to validate the count is not greater than expected), and each call included the correct expected JSON in the request body. Do I simply setup a couple dozen unique intercepts by aliasing individual requests based on request body inspection for the type
? https://docs.cypress.io/api/commands/intercept#Aliasing-individual-requests Or are there some other options I have not considered like some way to set a generic intercept against /events/
but a method to access the entire interception stack instead of popping from the stack using cy.wait("@{alias}")
?mysterious-belgium-25713
11/12/2022, 4:08 PMgray-kilobyte-89541
11/12/2022, 4:43 PMstale-furniture-7985
11/12/2022, 6:10 PMbumpy-exabyte-34804
11/12/2022, 10:05 PMstale-optician-85950
11/12/2022, 10:14 PMglamorous-planet-98729
11/13/2022, 9:54 AMstale-optician-85950
11/13/2022, 9:59 AMglamorous-planet-98729
11/13/2022, 11:05 AMglamorous-planet-98729
11/13/2022, 11:07 AMbumpy-exabyte-34804
11/13/2022, 11:18 AMadorable-photographer-47740
11/13/2022, 11:34 AMcareful-insurance-62240
11/13/2022, 2:23 PMglamorous-planet-98729
11/13/2022, 2:31 PMstale-optician-85950
11/13/2022, 3:29 PMnpm cypress cache clear
as shown in docs here https://docs.cypress.io/guides/guides/command-line#cypress-cache-clear and reinstall Cypress latest version.
You could also run npm cypress info
to view how your browsers are seen by Cypress and if everything is as you expect https://docs.cypress.io/guides/guides/command-line#cypress-info
Was your previous working version v10.x.x?
Also, if this is SOS in your framework just revert to the working version in the meantime. And debug version 11.0.1 on a branch safely, still allowing your CI tests to run in CI etcbillions-tomato-88210
11/13/2022, 5:03 PMgray-kilobyte-89541
11/13/2022, 10:40 PM