Have you followed these recipes: https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/fundamentals__dynamic-tests-from-csv or https://medium.com/@you54f/dynamically-generate-data-in-cypress-from-csv-xlsx-7805961eff55

Cypress 10 and connecting to an Oracle d...

Hello. I ask everyone for a help with my problem: I started to learn Cypress and have some bug with blank page when cypress visit address. How to solve it?

test work fine, but I don't see anything on screen.

this I can see directly in browser:

and everything looks fine until i run the test

Hi Team , Whiles testing login functionality on our application, After clicking on login - It redirects to Microsoft login - authentication page .... the page remains blank and only MS url is shown... Error Im getting is

However, added 'experimentalSessionAndOrigin' and 'experimentalStudio' as TRUE in - cypress.config.js

const { defineConfig } = require("cypress"); module.exports = defineConfig({ chromeWebSecurity: false, projectId: 'qsyx7s', e2e: { setupNodeEvents(on, config) { // implement node event listeners here }, "experimentalSessionAndOrigin": true, "experimentalStudio": true, }, });

Can someone help me with this ????

Hi All! In my tested app I'm using a WebGL based library I need to test. Since I cannot use visual testing for various reasons, I have exposed the library to the global namespace and I'm trying to spy on calls to this library methods. Some methods are asynchronous, though. I wasn't able so far to create a spy on a library method and verify its returned RESOLVED value was correct. If not - I need this to fail my whole test, naturally (some tests remain green though parts are failing):

Hi All! In my tested app I'm using a WebGL based library I need to test. Since I cannot use visual testing for various reasons, I have exposed the library to the global namespace and I'm trying to spy on calls to this library methods. Some methods are asynchronous, though. I wasn't able so far to create a spy on a library method and verify its returned RESOLVED value was correct. const fgspy = cy.spy(chart, 'foreground'); cy.get('.myButton').click(); fgspy.getCall(0).returnValue.then( res => { expect(fgRes.whatever).... }); I tried using WRAP but I had a couple of issues there: first - test was green though it failed assertions, second - I had a typing issue (working in TS). Any assistance will be much appreciated 🙂 !!!

Hi!! You try with another url? so you can see if there is a problem of the test or cypress

you can watch this tutorial, it´s great:

Hi team! someone who can help me with this error when executing a spec.cy.js. It's been several days and I haven't found a solution to this problem. Error: Webpack Compilation Error ./cypress/cert_pre/AmazonRootCA1.pem 1:4 Module parse failed: Assigning to rvalue (1:4) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.

Hi Team I got the same error as @limited-barista-33480 funny thing is that I was working on creating my test cases when suddenly it would not run that cy file and will give the error. Webpack Compilation Error ./cypress/POM/jobBriefPage.js Module not found: Error: Can't resolve 'cypress/types/jquery' in 'D:\Users\vhernandez\Docum resolve 'cypress/types/jquery' in 'D:\Users\vhernandez\Documents\Winmill\Cypress_Tests\cypr Parsed request is a module using description file: D:\Users\vhernandez\Documents\Winmill\Cypress_Tests\package.json Field 'browser' doesn't contain a valid alias configuration Looked for and couldn't find the file at the following paths:

Hey @limited-barista-33480 and @brief-restaurant-78755 , are you folks sure you haven't updated the Cypress to v10 in the meantime? If so, maybe you could double-check if you properly load the plugins file in that new version via

setupNodeEvents

. In order to make aliasing work in webpack, those need to be properly configured, and since v10, the plugins are no longer loaded by default. Here're the links to the docs: https://docs.cypress.io/guides/references/configuration#setupNodeEvents and https://docs.cypress.io/guides/tooling/plugins-guide#Using-a-plugin.

Hello. I have a test where I need to fill an iframe (Stripe payment iframe) where I enter credit card number,expiration date and cvc. My test works in following situations: 1. Cypress on local and remote env My test DOES NOT work in following situation: 2. Cypress as instance in gitlab CI/CD (gitlab runner) and the same remote env My code to access iframe cy.get(".__PrivateStripeElement > iframe").within(function($iFrame){ cy.wrap($iFrame.contents().find('body')).find('#Field-numberInput').type('4242').type('4242').type('4242').type('4242') cy.wrap($iFrame.contents().find('body')).find('#Field-expiryInput').type('12').type('34') cy.wrap($iFrame.contents().find('body')).find('#Field-cvcInput').type('123').type('{enter}') });

My error message on dashboard

Hello

Hey @victorious-father-41976 , now I have made some configurations of the awsit certificates and I have this problem when running a test from cypress in version 10. I don't know what this problem could be.

is anyone on version 10.x.x (10.8.0 for me) actually getting https://github.com/mfrachet/cypress-audit this to work properly? I have followed all directions here: https://mfrachet.github.io/cypress-audit/guides/lighthouse/installation.html#installing-the-dependency Here: https://glebbahmutov.com/blog/cypress-lighthouse/ but nothing gives. mostly my task just times out and it also opens up a new browser window every time which i believe isnt correct

so what is the error, im using with latest version of cypress and i dont see any issues

this example is working well https://github.com/mfrachet/cypress-audit/tree/master/examples/cra-authenticated

Hello I have a question regarding the use of custom classes with cypess e2e. I'm using Cypress with Typescript and have a Web-Page consisting of loads of different forms. I want to capsule every form and it's corresponding inputs into a custom class, which I then wanna use to write custom commands for easily checking different interactions of the forms. E.g.: I have a form consisting of three inputs with the ID's [firstname, lastname, birthplace]. I write a custom typescript class:

class Form{
  firstname?: string
  lastname?: string
  birthplace?: string

  constructor(...){...}

  setAllWrong(){
    this.firstname = ""
    this.lastname = ""
    this.birthplace = ""
  }
}

Now I declare a custom command:

Cypress.Commands.add(
    'fill_all_correct',
    (data: Form) => {
        ...
    }
)

And define it insinde the `index.ts`:

declare namespace Cypress {
  interface Chainable{
      fill_all_correct(data: Form): Chainable<Element>,
  }
}

Cypress is now giving me a

ReferenceError: Form is not defined

when using it inside a test.

specify('Test', () => {
         const form= new Form()
         ...
    }

Importing the

Form

Class inside the test, command and index file leaves me with an

Type 'Chainable' is not generic.

inside the

index.ts

. Can anybody identify what I may be doing wrong and what I should do instead ? I hope I could picture the problem for all of you.

my task sometimes times out, and when i see this actuall give LH results, its usually on my retry ( i have 2 retries) 1st one times out and somehow the 2nd one will run it when i set my specific it block to 0 retries it just times out, il try that example you provided, Thanks!!

hello, has anyone managed to perform a test where the mouse can drag a card to a container? trello card example

im using something like this, but it doesnt work for everything

cy.get(`#widget-edit-0-drag-handle`)
    .click()
    .trigger('mousedown', {which: 1, pageX: 0, pageY: 0});

cy.get(`#widget-edit-0-drag-handle`);
    .trigger('mousemove', 100, 100, {force: true})
    .trigger('mouseup');

Hi all! Is there some guide that people can point me to that works with iframe for Cypress 10? Been looking around and do try and error and having no success, so far.

Hi, I'm a little new to cypress but had a question regarding optimizing a block of locators with a similar name. The locators are in a dedicated locator file that is called from the main test script(similar to page object model). This is an example of the locators:

drawerAccordianContent1:
    '[data-testid="drawer-accordion-description-1"]',
  drawerAccordianContent2:
    '[data-testid="drawer-accordion-description-2"]',
  drawerAccordianContent3:
    '[data-testid="drawer-accordion-description-3"]',
  drawerAccordianContent4:
    '[data-testid="drawer-accordion-description-4"]',
  drawerAccordianContent5:
    '[data-testid="drawer-accordion-description-5"]',