Dynamic test data generation in Cypress - Test Execution Trace

Test Overview

This test generates a unique username dynamically and verifies that the registration form accepts it successfully.

Test Code - Cypress

Cypress

describe('User Registration with Dynamic Data', () => {
  it('should register a user with a unique username', () => {
    const uniqueUsername = `user_${Date.now()}`;
    cy.visit('https://example.com/register');
    cy.get('#username').type(uniqueUsername);
    cy.get('#email').type(`${uniqueUsername}@mail.com`);
    cy.get('#password').type('Password123!');
    cy.get('#register-btn').click();
    cy.get('.success-message').should('contain.text', 'Registration successful');
  });
});

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test runner initialized, no browser opened yet	—	PASS
2	Browser opens and navigates to 'https://example.com/register'	Registration page is loaded with username, email, password fields and register button	Page URL is correct and form elements are visible	PASS
3	Generates a unique username using current timestamp	Variable uniqueUsername holds a string like 'user_1687000000000'	uniqueUsername is a non-empty string with expected format	PASS
4	Finds username input field and types the unique username	Username input contains the unique username text	Input value matches uniqueUsername	PASS
5	Finds email input field and types email based on unique username	Email input contains text like '[e-mail]'	Input value matches generated email	PASS
6	Finds password input field and types 'Password123!'	Password input contains the typed password	Input value matches 'Password123!'	PASS
7	Finds and clicks the register button	Form is submitted, page processes registration	—	PASS
8	Checks for success message containing 'Registration successful'	Success message is visible on the page	Success message text contains 'Registration successful'	PASS

Failure Scenario

Failing Condition: The success message does not appear after form submission

Execution Trace Quiz - 3 Questions

What is the purpose of generating a unique username in this test?

A To avoid conflicts with existing users during registration

B To test the login functionality

C To check password strength validation

D To verify email format validation

Key Result

Generating dynamic test data like unique usernames helps avoid conflicts and makes tests reliable when running multiple times.

Practice

1. What is the main benefit of using dynamic test data generation in Cypress tests?

easy

A. It creates unique data for each test run to avoid conflicts.

B. It makes tests run slower by adding delays.

C. It hardcodes values to ensure consistency.

D. It disables assertions to speed up tests.

Solution

1. Step 1: Understand dynamic data purpose

   Dynamic test data generation creates fresh data each time to prevent clashes with existing data.

2. Step 2: Compare options

   Only It creates unique data for each test run to avoid conflicts. describes this benefit correctly; others describe incorrect or unrelated effects.

3. Final Answer:

   It creates unique data for each test run to avoid conflicts. -> Option A

4. Quick Check:

   Dynamic data = unique per run [OK]

Hint: Dynamic data means fresh unique values each test run [OK]

Common Mistakes:

• Thinking dynamic data slows tests
• Confusing dynamic with hardcoded data
• Believing dynamic data disables assertions

2. Which of the following is the correct way to generate a random email in Cypress using JavaScript template literals?

easy

A. const email = user${Math.random()}@test.com;

B. const email = 'user' + Math.random() + '@test.com';

C. const email = `user+Math.random()@test.com`;

D. const email = `user${Math.random()}@test.com`;

Solution

1. Step 1: Identify correct template literal syntax

   Template literals use backticks and ${} to embed expressions, so `user${Math.random()}@test.com` is correct.

2. Step 2: Check other options

   const email = 'user' + Math.random() + '@test.com'; uses string concatenation, which works but is not template literals. const email = user${Math.random()}@test.com; misses backticks. const email = `user+Math.random()@test.com`; treats Math.random() as string literal.

3. Final Answer:

   const email = `user${Math.random()}@test.com`; -> Option D

4. Quick Check:

   Template literals use backticks and ${} [OK]

Hint: Template literals use backticks and ${expression} [OK]

Common Mistakes:

• Using quotes instead of backticks for template literals
• Forgetting ${} around expressions
• Treating expressions as plain text

3. Given the Cypress code snippet:

const randomId = Math.floor(Math.random() * 1000);
cy.get('#user-input').type(`user${randomId}`);
cy.get('#submit-btn').click();
cy.get('#result').should('contain', `user${randomId}`);

What will the assertion check?

medium

A. That the element with id 'result' contains a random number only.

B. That the element with id 'result' contains the text 'user' only.

C. That the element with id 'result' contains the exact text 'user' plus the random number generated.

D. That the element with id 'result' contains the string 'randomId'.

Solution

1. Step 1: Understand variable usage in template literals

   The variable randomId is generated once and used in the string `user${randomId}` for typing and assertion.

2. Step 2: Analyze assertion

   The assertion checks if '#result' contains the exact string 'user' concatenated with the random number stored in randomId.

3. Final Answer:

   That the element with id 'result' contains the exact text 'user' plus the random number generated. -> Option C

4. Quick Check:

   Assertion checks full dynamic string [OK]

Hint: Assertions check exact dynamic string used in test [OK]

Common Mistakes:

• Assuming assertion checks only 'user' text
• Thinking random number is checked alone
• Confusing variable name with string literal

4. Identify the error in this Cypress test code that tries to generate a random username:

const username = 'user' + Math.random;
cy.get('#username').type(username);
cy.get('#submit').click();

medium

A. The username variable should be declared inside the test only.

B. Math.random is missing parentheses, so it is a function reference, not a number.

C. The selector '#username' is invalid and should be '.username'.

D. The click command is missing parentheses.

Solution

1. Step 1: Check Math.random usage

   Math.random is a function and must be called with parentheses to get a number. Without (), username becomes 'user' plus function reference string.

2. Step 2: Verify other parts

   Selectors and click command syntax are correct. The main error is missing parentheses on Math.random.

3. Final Answer:

   Math.random is missing parentheses, so it is a function reference, not a number. -> Option B

4. Quick Check:

   Call Math.random() with () to get number [OK]

Hint: Always call Math.random() with parentheses [OK]

Common Mistakes:

• Forgetting parentheses on Math.random
• Misreading selector syntax
• Thinking click needs extra parentheses

5. You want to generate a dynamic user object with unique email and username for each Cypress test run. Which approach correctly creates this object and uses it in a test?

const user = {
  username: `user${Math.floor(Math.random() * 10000)}`,
  email: `email${Math.floor(Math.random() * 10000)}@test.com`
};

cy.visit('/signup');
cy.get('#username').type(user.username);
cy.get('#email').type(user.email);
cy.get('#submit').click();
cy.get('#welcome').should('contain', user.username);

hard

A. This approach correctly generates unique user data and uses it in the test assertions.

B. This approach fails because Math.random() should not be used for test data.

C. This approach is incorrect because user object must be inside cy.then() callback.

D. This approach is wrong because template literals cannot be used inside objects.

Solution

1. Step 1: Analyze user object creation

   The user object uses template literals with Math.floor(Math.random() * 10000) to create unique username and email strings before the test runs.

2. Step 2: Check usage in Cypress commands

   The test types the dynamic username and email into inputs, clicks submit, and asserts the welcome message contains the username, which is valid and correct.

3. Final Answer:

   This approach correctly generates unique user data and uses it in the test assertions. -> Option A

4. Quick Check:

   Dynamic object with random values used correctly [OK]

Hint: Create dynamic objects before test, then use in commands [OK]

Common Mistakes:

• Thinking Math.random() is disallowed for test data
• Believing object must be inside cy.then() unnecessarily
• Misunderstanding template literal usage inside objects