ah thanks. It was actually the same outcome - but I figured out the issue. It does actually allow me to run both types of tests I just need to NOT try to run my cypress cucumber spec implementation as a test itself. Basically I want to hide my cucumber implementation js files (see attached photo) I think I can figure that out though, but please do let me know if you have any thoughts! Cheers

hi all, is there a way to monitor the cypress backend api requests I make on task files? It would be great to have insight on what's currently being called on the background

use ignore test files option to exclude files that you want to hide

Hi all, When running cypress it "gets stuck" meaning that I cannot continue with the script or Manually Clicking on any element. This happens when there is a loader. if the web page has to pull information from the loader then this is where cypress stops working, I re loads the page I clicked on and then there is nothing I can click on anymore

thanks again!

yeah for some reason that does not work. I am not sure why but it seems to run anyway.

Read https://on.cypress.io/troubleshooting#Log-sources and check what it does while searching for specs

Has Anyone been able to succesfully test Salesforce? once it logs in, it opens another browser window outside of cypress

No, this is just example code. Not sure why it was not working, but changed the code and then for some reason I was not getting data from the fixture. It turns out that my json had the wrong response. Oooh!!!!! Thanks for your help. Much appreciated.

Is this of any help? https://medium.com/smartbox-engineering/using-cypress-to-test-in-salesforce-a0699afe09b7

Hi all, happy New Year!! I'm using dataSession and for some reason it always gets recomputed when I execute a new test. It delivers this message, and then reloads the whole runner with a new resolution and re-executes the dataSession. Anyone have encountered this?

dataSession data1
dataSession:load, dataSession:data1
readFileMaybe, ./cypress/generatedData/file.json
recomputing data1 because a parent session has been recomputed
recompute data for data1

Can you provide a reproducible example? Also make sure to use the latest released version

https://stackoverflow.com/questions/70604946/modify-fixture-data-in-cypress-and-intercept-it how do I create 'dynamic' fixture using code guys?

Hi @stocky-dream-36427 Do you know of you any GitHub project that is actively using Cypress for testing, also which according to you can be a good project to learn from?

Hello!

We have a big project called the Real World Testing App.

This shows the extremes of testing a large app.

However... if you just scaffold out a new Cypress project, you'll be greeted with a lot of example files! Each of these spec files is named after a core piece of the Cypress API.

Thank you.

hi @User , sorry for the delay. Im not sure now if it's strictly related to the usage of dataSession (although I've noticed it while using it). You can see it happening here:

I'm using a dedicated test repo, which is then added as a subtree for the apps' repos. When the tests are run on the test repo CI, I can test the whole app suite (as they share the same domain). But when running locally, it's only possible to run the tests of each project at a time (which I group by using grepTags). I use envVariables to point to each of the projects URL, so when I want to run on one project only, I can change this envVar to localhost:3000 and grep only the tests for this project. So it seems that Cypress first loads the standard envVars in .env, but then reloads with the inline defined envVars.

ohh, because the baseUrl changes, it reloads the spec. Probably can use shareAcrossSpecs: true option to store the data in the plugins process to survive the reloads

I'm using that already :/ it still recomputes. If there's no way to workaround the reloads, then probably I'll have to look for another solution for change the URL used

the only strange thing is that Im not changing baseurl directly, only updating an unrelated envVar value. thanks for the feedback though

I try to test a TYPO3 Backend Module. Maybe I'm crazy, but I want to give it a try 😉 My problem is now, that after the login, I receive a lot of JS errors, because TYPO3 ist using "top.TYPO3" as global object. But since cypress is running in an iframe too, I suspect, that this object is outside the context of my test. Has anybody an idea, what i could do?

when I try "modifyObstructiveCode": false, my test is not running at all. The test starts and after a second, I get "Whoops, there is no test to run"

@icy-energy-70840 👋 how do you do

@brainy-photographer-13281 Hey, Welcome

Hi all, hope you're having good testing!. I stumbled upon an issue when logging in 2 different environments: one is staging, the other, localhost:3000. The current process is to make a call to an API, which does the GoogleOauth and returns the tokens, then we add it as a key in sessionStorage and refresh the page. When I do that manually in the browser, I can login in on both environments, however on automation, it doesn't work well in the staging (.dev) environment, as it simply stays at the login page. It works perfectly on the local server. Does any one knows how could I get some meaningful debugging for this situation? As it seems to be a browser-side complexity Nvm, fixed completely using cy.session to better manage the cached data

Good night, I'm fussing with cypress, I don't understand how I can make cypress wait for an api call to be resolved and only then validate a modal that will display an error or success message