Test naming conventions in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use descriptive test names?

In Cypress testing, why is it important to use descriptive and clear test names?

A To make test reports easy to understand and help quickly identify what each test checks.

B To reduce the test execution time by shortening the test code.

C To allow Cypress to automatically fix failing tests based on the name.

D To make tests run in parallel without conflicts.

💡 Hint

Think about how test names help when reading test results or debugging.

Descriptive test names help testers and developers quickly understand what each test does. This makes debugging and maintaining tests easier.

❓ Predict Output

intermediate

Output of test name in Cypress report

What will be the test name shown in Cypress test report for the following code?

Cypress

describe('Login Page', () => {
  it('should display error on invalid credentials', () => {
    // test steps
  })
})

A Login Page should display error on invalid credentials

B should display error on invalid credentials

C describe Login Page it should display error on invalid credentials

D Login Page > should display error on invalid credentials

💡 Hint

Consider how Cypress combines describe and it blocks in reports.

Cypress shows test names by combining the describe block and the it block separated by a > symbol.

❓ assertion

advanced

Best practice for test name format

Which of the following test names follows best practice for naming Cypress tests?

A "test_login_error"

B "LoginTest1"

C "should show error message when login fails"

D "Check login error"

💡 Hint

Good test names describe behavior clearly and use readable language.

Option C clearly describes the expected behavior in a readable sentence, which is best practice.

🔧 Debug

advanced

Identify the poorly named test

Which test name below is the least helpful for understanding the test purpose?

A "Verify user can logout successfully"

B "Test case 5"

C "should redirect to dashboard after login"

D "Displays error for empty password field"

💡 Hint

Look for names that do not describe what the test does.

"Test case 5" is vague and does not describe the test purpose, making it hard to understand or debug.

❓ framework

expert

How to enforce test naming conventions in Cypress

Which approach is best to enforce consistent test naming conventions across a Cypress test suite?

A Use a linter plugin configured to check test name patterns in <code>it</code> and <code>describe</code> blocks.

B Manually review all test names during code reviews without any automated tool.

C Write tests only with short names to avoid complexity.

D Rely on Cypress default naming without any additional checks.

💡 Hint

Think about automation tools that help maintain code quality.

Using a linter plugin to check test names automatically ensures consistent naming and reduces human error.