Dynamic test data generation in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress test snippet?

Consider this Cypress test code that generates dynamic user data and asserts the username length.

Cypress

const username = `user_${Math.floor(Math.random() * 1000)}`;

it('checks username length', () => {
  expect(username.length).to.be.greaterThan(5);
});

A Test fails because username length is always less than 5

B Test sometimes passes or fails depending on random number

C Test passes because username length is always greater than 5

D Test throws an error due to syntax mistake

💡 Hint

Think about the minimum length of the username string generated.

The username starts with 'user_' which is 5 characters, plus at least one digit from the random number, so length is always greater than 5. The test always passes.

❓ assertion

intermediate

Which assertion correctly verifies a dynamically generated email format?

You generate an email dynamically in Cypress as const email = `test${Date.now()}@example.com`;. Which assertion correctly checks the email format?

A expect(email).to.match(/^[\w.-]+@[\w.-]+\.com$/);

B expect(email).to.include('@example.com');

C expect(email).to.equal('[e-mail]');

D expect(email).to.have.length(10);

💡 Hint

Check which option validates the email pattern properly.

Option A uses a regex to check the email format including username and domain. Option A only checks substring, A expects exact string which is wrong, D checks length which is arbitrary.

🔧 Debug

advanced

Why does this dynamic data test fail intermittently?

Look at this Cypress test that fills a form with dynamic data:

const userId = Math.floor(Math.random() * 10);
cy.get('#user-id').type(userId.toString());
cy.get('#submit').click();
cy.get('#result').should('contain', `User ID: ${userId}`);

Sometimes the test fails with a mismatch error. Why?

A The random userId is generated outside the test, causing stale value issues

B The selector '#user-id' is incorrect and causes failure

C The test runs too fast and the page does not update in time

D The userId is a number but should be a string for typing

💡 Hint

Consider when the random value is generated and how Cypress commands queue.

The userId is generated once when the test file loads, but Cypress commands run asynchronously later. This can cause mismatch if the page updates or reloads. Generating userId inside the test ensures fresh value.

❓ framework

advanced

Which Cypress command correctly generates and uses dynamic test data for multiple tests?

You want to generate a unique username for each test run and reuse it in multiple tests. Which approach is best?

A Use <code>beforeEach(() =&gt; { cy.wrap(`user_${Date.now()}`).as('username'); });</code> and access with <code>this.username</code> in tests

B Generate username in <code>before()</code> hook and save to a variable outside tests

C Generate username inside each test separately to avoid sharing

D Use <code>Cypress.env('username')</code> set dynamically before tests

💡 Hint

Think about scope and sharing data between tests in Cypress.

Generating username in before() runs once before all tests, saving to a variable accessible by all tests. Option B uses alias but this context is unreliable in arrow functions. Option B duplicates data. Option B requires external setup.

🧠 Conceptual

expert

What is the main benefit of dynamic test data generation in automated tests?

Choose the best explanation for why dynamic test data generation is important in automated testing.

A It guarantees tests will never fail due to data issues

B It makes tests run faster by avoiding hardcoded values

C It simplifies test code by removing the need for assertions

D It prevents tests from using stale or duplicate data, improving test reliability and coverage

💡 Hint

Think about how dynamic data affects test results and maintenance.

Dynamic data helps avoid conflicts from repeated use of same data, reduces false failures, and tests more scenarios. It does not guarantee no failures or faster tests, nor removes assertions.