Cypress Top Interview Questions and Answers Part - 7

1.How to access data from fixtures?

Ans:

In Cypress, fixtures are used to store and load external data files for testing purposes. Fixtures can contain JSON, XML, CSV, or any other supported file format. To access data from fixtures in your Cypress tests, you can follow these steps:

Inside the fixtures directory, create a data file with the desired format (e.g., data.json, data.csv, etc.) and populate it with the necessary data for your tests. For example:

json

// cypress/fixtures/data.json

{

? "username": "[email protected]",

? "password": "password123"

}

In your test file, you can use the cy.fixture() command to load the fixture data. The cy.fixture() command returns a Promise that resolves to the loaded fixture data. Here's an example of how to use it:

?javascript

// cypress/integration/example.cy.js

?describe('Example Test', () => {

? it('should log in successfully using fixture data', () => {

??? cy.fixture('data.json').then((data) => {

????? cy.login(data.username, data.password);

????? // ...

??? });

? });

});

In this example, the cy.fixture('data.json') command loads the data.json fixture file. The loaded data is then passed to the .then() callback, where you can access the data and use it in your test.

You can now use the loaded fixture data in your test commands. In the example above, the cy.login() command uses the username and password values from the loaded fixture data.

?By using fixtures and the cy.fixture() command, you can easily organize and load external data into your Cypress tests. This allows you to separate your test data from your test code, making it more manageable and reusable. You can create multiple fixture files to store different sets of data and load them as needed in your tests.

2.How to work with hidden elements with cypress?

Ans:

1.?.invoke('show') Method: If you need to make a hidden element visible before interacting with it, you can use the .invoke('show') method to modify the element's CSS display property and make it visible. For example

???????????????? cy.get('.hidden-element').invoke('show');

2.?cy.get(“element”).click({force:true})

3.How to re-run the failed test cases.?

Ans:

To rerun failed test cases in Cypress, you can make use of Cypress' built-in retry functionality and test retries. Here's how you can configure Cypress to automatically rerun failed tests:

?Open your cypress.config.js file in your Cypress project's root directory.

?Add the following configuration to enable test retries:

{

? "retries": {

??? "runMode": 2,

??? "openMode": 2

? }

}

The "runMode" and "openMode" options set the number of times Cypress will automatically retry failed tests when running in "run" mode (e.g., cypress run) and "open" mode (e.g., cypress open), respectively. In the example above, the value of 2 indicates that failed tests will be retried once.

4.How to set default command timeout and page load timeout or What are time outs in cypress?

Ans:

In Cypress, you can set the default command timeout and page load timeout by configuring the Cypress configuration options. Here's how you can set these timeouts:

?Open your cypress.config.js file in your Cypress project's root directory.

?Add the following configuration options to specify the desired timeouts:

?{

? "defaultCommandTimeout": 5000,

? "pageLoadTimeout": 10000

}

"defaultCommandTimeout": Sets the maximum time (in milliseconds) that Cypress will wait for each command to complete. If a command takes longer than this timeout, Cypress will consider it as a failure. In the example above, the default command timeout is set to 5 seconds (5000 milliseconds).

"pageLoadTimeout": Sets the maximum time (in milliseconds) that Cypress will wait for a page to finish loading before considering it as a failure. This timeout is applicable to cy.visit() and other navigation-related commands. In the example above, the page load timeout is set to 10 seconds (10000 milliseconds).

?The Other explicit time is

?cy.get(“locator”, {timeout: 20000}).click()

Other wait is hard wait

cy.wait(1000)

5.How to work with different environment (qa, preprod, prod) in cypress?

Ans:

Working with different environments (e.g., QA, preprod, prod) in Cypress involves managing configuration files and specifying environment-specific variables. Here's how you can work with different environments in Cypress:

?Create Configuration Files: Create separate configuration files for each environment you want to work with. For example, you can create cypress.qa. json, cypress.preprod.json, and cypress.prod.json files.

?Configure Environment-Specific Variables: In each configuration file, define environment-specific variables such as URLs, API endpoints, database connections, or any other configuration values specific to that environment. For example:

// cypress.qa.json

?{

? "baseUrl": "https://qa.example.com",

? "apiEndpoint": "https://api.qa.example.com",

? "databaseUrl": "mongodb://qa.example.com"

}

Configure Cypress to Use Environment-Specific Configuration: Open your cypress.config.js file in your Cypress project's root directory and add a env section to specify which configuration file to use for each environment. For example:

{

? "baseUrl": "https://www.example.com",

? "env": {

??? "qa": {

????? "configFile": "cypress.qa.json"

??? },

??? "preprod": {

????? "configFile": "cypress.preprod.json"

??? },

??? "prod": {

????? "configFile": "cypress.prod.json"

??? }

? }

}

Access Environment Variables in Tests: In your Cypress test files, you can access the environment-specific variables defined in the configuration files using Cypress.env() method. For example:

// Accessing environment-specific variables

const baseUrl = Cypress.env('baseUrl');

const apiEndpoint = Cypress.env('apiEndpoint');

Run Tests with Specific Environment: To run your tests with a specific environment configuration, use the --env flag when executing the Cypress command. For example, to run tests with the QA environment configuration, use:

cypress run --env qa

By following these steps, you can manage different environments in Cypress by creating separate configuration files and specifying environment-specific variables. This allows you to easily switch between environments and customize the test behavior based on the specific environment requirements.