Skipping and focusing tests (.skip, .only) in Cypress - Framework Patterns

Framework Mode - Skipping and focusing tests (.skip, .only)

Folder Structure for Cypress Test Framework

cypress/
├── e2e/                  # Test files (specs) go here
│   ├── login.spec.js     # Example test file
│   └── dashboard.spec.js
├── fixtures/             # Test data files (JSON, etc.)
│   └── users.json
├── support/              # Support files and commands
│   ├── commands.js       # Custom commands
│   └── e2e.js            # Global setup
cypress.config.js         # Cypress configuration file
package.json              # Project dependencies and scripts

Test Framework Layers in Cypress

• Test Layer (cypress/e2e): Contains test files where you write your test cases using describe and it. Here you use .skip and .only to control which tests run.
• Support Layer (cypress/support): Contains reusable commands and global setup to keep tests clean.
• Fixtures Layer (cypress/fixtures): Holds test data files to separate data from test logic.
• Configuration Layer (cypress.config.js): Defines environment settings, base URLs, and browser options.

Configuration Patterns for Skipping and Focusing Tests

Use .skip and .only directly in test files to control test execution:

• describe.skip('Feature', () => { ... }) skips all tests in this group.
• it.skip('should do something', () => { ... }) skips a single test.
• describe.only('Feature', () => { ... }) runs only this group, skipping others.
• it.only('should do something', () => { ... }) runs only this test.

Use environment variables in cypress.config.js or package.json scripts to control which tests run dynamically if needed.

Test Reporting and CI/CD Integration

• Use Cypress built-in reporters or plugins like mochawesome for detailed reports.
• Configure CI/CD pipelines (GitHub Actions, Jenkins, etc.) to run tests with commands like npx cypress run.
• Ensure skipped tests are reported clearly to avoid confusion.
• Use focused tests (.only) carefully to avoid missing test coverage in CI.

Best Practices for Skipping and Focusing Tests

1. Use .skip to temporarily disable flaky or incomplete tests but remove skips before final commits.
2. Use .only locally to focus on debugging but never commit .only to shared branches.
3. Keep skipped tests documented with comments explaining why they are skipped.
4. Use environment variables or tags for conditional test runs instead of relying heavily on .skip or .only.
5. Regularly review skipped tests to avoid forgotten or stale tests.

Self Check Question

Where in this Cypress framework structure would you add describe.only to run only the login tests?

Key Result

Use .skip and .only in Cypress test files to control which tests run during development and debugging.

Practice

1. What does the .skip method do in Cypress testing?

easy

A. It skips the marked test or group so it does not run.

B. It runs only the marked test or group and skips others.

C. It marks the test as failed automatically.

D. It retries the test multiple times before failing.

Solution

1. Step 1: Understand the purpose of .skip

   The .skip method is used to tell Cypress to ignore a test or group during execution.

2. Step 2: Compare with other methods

   Unlike .only, which runs only the marked tests, .skip prevents the marked tests from running.

3. Final Answer:

   It skips the marked test or group so it does not run. -> Option A

4. Quick Check:

   .skip = skip test [OK]

Hint: Remember: skip means ignore this test [OK]

Common Mistakes:

• Confusing .skip with .only
• Thinking .skip runs the test
• Assuming .skip marks test as failed

2. Which of the following is the correct syntax to run only one test in Cypress?

easy

A. it.skip('test name', () => { /* test code */ })

B. describe.only('group name', () => { /* tests */ })

C. it.only('test name', () => { /* test code */ })

D. describe.skip('group name', () => { /* tests */ })

Solution

1. Step 1: Identify the method to run only one test

   The it.only syntax runs only the marked test and skips all others.

2. Step 2: Check other options

   it.skip skips a test, describe.only runs only a group, and describe.skip skips a group.

3. Final Answer:

   it.only('test name', () => { /* test code */ }) -> Option C

4. Quick Check:

   it.only runs only one test [OK]

Hint: Use it.only to run just one test [OK]

Common Mistakes:

• Using describe.only to run a single test
• Confusing skip and only syntax
• Forgetting parentheses in function

3. Given the code below, which tests will run?

describe('Group A', () => {
  it('Test 1', () => { /* code */ })
  it.only('Test 2', () => { /* code */ })
  it('Test 3', () => { /* code */ })
})
describe.only('Group B', () => {
  it('Test 4', () => { /* code */ })
  it('Test 5', () => { /* code */ })
})

medium

A. All tests in both groups run.

B. All tests in Group A run except Test 2.

C. Only Test 2 runs, Group B tests are skipped.

D. Only all tests in Group B run.

Solution

1. Step 1: Understand describe.only effect

   The describe.only('Group B') means only Group B runs; Group A is skipped.

2. Step 2: Understand it.only inside Group A

   Even though it.only('Test 2') is inside Group A, Group A is skipped entirely because of describe.only on Group B.

3. Step 3: Determine which tests run

   All tests inside Group B run (Test 4 and Test 5). Test 2 does not run because Group A is skipped.

4. Final Answer:

   Only all tests in Group B run. -> Option D

5. Quick Check:

   describe.only overrides it.only [OK]

Hint: describe.only runs only that group, ignoring it.only inside others [OK]

Common Mistakes:

• Thinking it.only inside skipped describe runs
• Ignoring describe.only effect
• Assuming all tests run

4. You have this Cypress test code:

describe.skip('Group X', () => {
  it.only('Test A', () => { /* code */ })
  it('Test B', () => { /* code */ })
})
describe('Group Y', () => {
  it('Test C', () => { /* code */ })
})

What is the problem with this code?

medium

A. Test C will run but Group X tests will be skipped.

B. Test A will run but Test B and Test C will be skipped.

C. Test A will run but Group Y tests will be skipped.

D. No tests will run because the entire Group X is skipped.

Solution

1. Step 1: Analyze describe.skip effect on Group X

   The entire Group X is skipped, so none of its tests run, including it.only.

2. Step 2: Analyze Group Y tests

   Group Y is not skipped, so its test (Test C) runs normally.

3. Final Answer:

   Test C will run but Group X tests will be skipped. -> Option A

4. Quick Check:

   describe.skip skips whole group, ignoring it.only [OK]

Hint: describe.skip disables all tests inside, even it.only [OK]

Common Mistakes:

• Assuming it.only overrides describe.skip
• Thinking some tests in skipped group run
• Confusing which group is skipped

5. You want to run only a specific test inside a group but also skip another test in the same group. Which is the correct way to do this?

describe('My Tests', () => {
  it('Test 1', () => { /* code */ })
  it('Test 2', () => { /* code */ })
  it('Test 3', () => { /* code */ })
})

Options: A) Add .only to Test 2 and .skip to Test 3. B) Add .skip to Test 1 and .only to Test 3. C) Add .only to Test 1 and .skip to Test 2. D) Add .skip to Test 2 and .skip to Test 3.

hard

A. Add .skip to Test 1 and .only to Test 3.

B. Add .only to Test 2 and .skip to Test 3.

C. Add .only to Test 1 and .skip to Test 2.

D. Add .skip to Test 2 and .skip to Test 3.

Solution

1. Step 1: Understand .only and .skip usage

   Using .only on a test runs only that test, skipping all others unless they also have .only. Using .skip skips that test.

2. Step 2: Apply to given tests

   To run only Test 2 and skip Test 3, add .only to Test 2 and .skip to Test 3. Test 1 will be skipped automatically because of .only.

3. Final Answer:

   Add .only to Test 2 and .skip to Test 3. -> Option B

4. Quick Check:

   .only runs test, .skip skips test [OK]

Hint: Use .only on test to run, .skip on test to ignore [OK]

Common Mistakes:

• Adding .only to multiple tests without need
• Skipping tests that .only already excludes
• Confusing which test to skip or run