How to use getComponentDisplayName method in Cypress

Try adding a click() before you type:

cy.get('#reasonRecommendationByAgent')
  .click()
  .type('Zdůvodnění doporučení zprostředkovatele', {force: true})
  .should('have.value', 'Zdůvodnění doporučení zprostředkovatele')

For the record, I found a great example here

Cypress examples (v9.4.1) - Form validation

<form id="form-validation" action="/action_page.php">
  <div>
    <label for="item">Item:</label>
    <input id="item" type="text" name="item" required />
  </div>

cy.get('#item:invalid')
  .invoke('prop', 'validationMessage')
  .should('equal', 'Please fill out this field.')

Solution 1:

You can use the wrap() method which yields the object passed as a param if it resolves like so:

context('Travel Portal Regression Test', () => {
  beforeEach(() => {
    cy.fixture('travelData').then((data) => cy.wrap(data).as('getTravelData'));
    // cy.viewport('iphone-6')
    cy.viewport(360, 640);
    cy.visit('https://thoughtcoders.com/');
  });

  it('Testing ThoughtCoders Homepage', () => {
    cy.log('Testing ThoughtCoders Homepage');
    cy.get('@getTravelData').then((res) => cy.log(res.FIRSTNAME));
  });
});

Solution 2:

You can declare a variable called travelData on the upper scope of your test spec & reassign its value to data received from the json file like so:

context('Travel Portal Regression Test', () => {
  let travelData;

  beforeEach(() => {
    cy.fixture('travelData').then((data) => {
      travelData = data;
      return travelData;
    });
    // cy.viewport('iphone-6')
    cy.viewport(360, 640);
    cy.visit('https://thoughtcoders.com/');
  });

  it('Testing ThoughtCoders Homepage', () => {
    cy.log('Testing ThoughtCoders Homepage');
    cy.log(travelData.FIRSTNAME);
  });
});

Here it's the screenshot with the test results:

probably you need to add some waiting time because your page its reloaded after switching the language maybe you need to check if your element already appear in the Dom with should('be.visible') this will add some waiting time by trying to check if the element is ready .

cy.visit('https://salaenrollment.com/')

cy.contains('ភាសាខ្មែរ').click()
  .url().should('include', '/kh')

cy.contains('ភាសាខ្មែរ').should('be.visible')

cy.contains('ទំនាក់ទំនង').should('have.attr', 'href', '/kh/contact')
  .click()

It looks like you are modifying a test file within the Cypress installation. This is probably not what you meant to do.

There are two important components to Cypress:

1. The Cypress package installation. In your case this is installed at c:\node_modules\.bin\cypress
2. The Project under test also has some Cypress related files, including cypress.json in the top level directory of the project, and the test files located in the cypress folder within the project directory (unless you have told Cypress to use a different directory).

When you run Cypress tests on a project, the test files which are watched are those that are located within the project directory - not those within the Cypress installation itself.

When you run cypress open then you can manually select the directory of the project that you want to test, say it is C:\MY_PROJECT. If there is no cypress.json file and no tests found, Cypress will automatically create a cypress.json file and a cypress directory within C:\MY_PROJECT. Inside the C:\MY_PROJECT\cypress\integration\ directory will be some example tests. When you edit tests in this directory with watchForFileChanges=true and manually choosing C:\MY_PROJECT to test, they will automatically rerun when saved.

I have also tested running and modifying the tests in the example directory within the Cypress package within the node_modules directory. I can confirm that when files within that directory are edited, the tests do not rerun. However, it is a mistake to edit those files when you are trying to test one of your own projects.

HTH

It is very difficult to test a situation where an action has not occured. With this type of assertion, you can really only say:

"The XHR request was not made within the 400ms that Cypress looked for this XHR request to have been made (or whatever you set your timeout to be)"

This doesn't really confirm that the XHR request was never called.

That being said, Cypress offers a way to retrieve all XHR requests made using the undocumented cy.state('requests'). You could check the length of that, filter them by alias, etc to probably determine what you want.

Yes, it looks like there is a good attempt to create a scenario recorder and it works to a great extent:

https://chrome.google.com/webstore/detail/cypress-scenario-recorder/fmpgoobcionmfneadjapdabmjfkmfekb/related?hl=en

to run only one file

cypress run --spec path/to/file.spec.js

or using glob patterns:

cypress run --spec 'path/to/files/*.spec.js'

Note: you need to wrap your glob patterns in single quotes to avoid shell expansion!

to run only one test in a file

You can use a .only as described in the Cypress docs

it.only('only run this one', () => {
  // similarly use it.skip(...) to skip a test
})

it('not this one', () => {
})

Also, you can do the same with describe and context blocks

edit:

there's also a nice VSCode extension to make adding/removing .only's easier with keyboard shortcuts. It's called Test Utils (install with ext install chrisbreiding.test-utils). It works with js, coffee, and typescript:

Don't know if this is going to help you or if you already fixed it, but I did find a solution to access an iframe inside another iframe, cause I was trying to solve that issue for myself, will leave the answer here and hope it can help.

So an example of the id of the iframes:

• Iframe1, id='first_iframe"
• Iframe2, id='second_iframe"

Here is the code sample you can try:

cy.get('#first_iframe').then($firstIframe => {
  const $secondIframeReference = $firstIframe.contents().find('#second_iframe');

  cy.wrap($secondIframeReference).as('secondIframeReference'); // Saving this as a reference so we can access it again using get command

  // Now we are accessing the second iframe
  cy.get('@secondIframeReference').then($secondIframe => {
    const $elementYouWant = $secondIframe.contents().find('element you want to interact with');

    cy.wrap('$elementYouWant').type("It's writing some stuff"); // In case it is an input field, for example
  });
});

Got into this solution after reading this article