Cypress: run only one test

JavascriptAutomated TestsCypressE2e Testing

Javascript Problem Overview


I want to toggle only running one test, so I don't have to wait for my other tests to see the result of one test.

Currently, I comment out my other tests, but this is really annoying.

Is there a way to toggle only running one test in Cypress?

Javascript Solutions


Solution 1 - Javascript

to run only one file
cypress run --spec path/to/file.spec.js

or using glob patterns:

cypress run --spec 'path/to/files/*.spec.js'

> Note: you need to wrap your glob patterns in single quotes to avoid shell expansion!

to run only one test in a file

You can use a .only as described in the Cypress docs

it.only('only run this one', () => {
  // similarly use it.skip(...) to skip a test
})

it('not this one', () => {
})

Also, you can do the same with describe and context blocks

edit:

there's also a nice VSCode extension to make adding/removing .only's easier with keyboard shortcuts. It's called Test Utils (install with ext install chrisbreiding.test-utils). It works with js, coffee, and typescript:

enter image description here

Solution 2 - Javascript

There are multiple ways of achieving this.

  1. You can add .onlyto it or describe see @bkucera answer
  2. You can do it from the terminal as explained in the doc here > > npx cypress run --record --spec "cypress/integration/my-spec.js" >
    > npm run cypress -- --record --spec "cypress/integration/my-spec.js"

Solution 3 - Javascript

You can mute not needed test suites and particular cases by prepending x to testrunner methods call (describe, it, etc.)

So it would look like:

// this whole testsuite will be muted
xdescribe('Visit google', () => { 
  it('should visit google', () => { cy.visit('https://google.com/'); });
});

// this testsuite will run
describe('Visit youtube', () => {
  it('should visit youtube', () => { cy.visit('https://youtube.com/'); });

  // this testcase will be muted
  xit('is not necessary', () => { ... });
});

Solution 4 - Javascript

There is one way I have found to skip tests which I don't need to run (in the current test), and that is to use: this.skip();

it('test page', function () {
    // skip this test for now
    this.skip();
    cy.visit('http://example.com/')
    cy.contains('test page').click()
    cy.url()
        .should('include', '/test-page/')
})

1. it is important to use regular function as second argument of it, this will not be available in arrow function
2. Whole of the test will be skipped no matter where we write this.skip()

Solution 5 - Javascript

You can run the test like this.

cypress run --spec **/file.js

Solution 6 - Javascript

The best way to do such kind runs are by using the .only keyword that cypress provide.

To run all the test cases in one describe function from many describe functions add the .only in the required describe.

describe("1st describe", () => {
  it("Should check xx", async function(){
  });
  it("Should check yy", async function(){
  });
});   
describe.only("2nd describe", () => {
  it("Should check xx", async function(){
  });
  it("Should check yy", async function(){
  });
}); 
describe("3rd describe", () => {
  it("Should check xx", async function(){
  });
  it("Should check yy", async function(){
  });
}); 

So here only the 2nd describe will run.

Similarly if you want to run some test cases in 1 describe add the .only in front of all the test cases that you want to run.

describe("describe statement", () => {
  it("Should check xx", async function(){
  });
  it.only("Should check yy", async function(){
  });
  it.only("Should check zz", async function(){
  });
});

So here the it for yy and zz will run

This is similar to the fit and fdescribe in karma and jasmine that you might be familiar with.

You can skip the test in cypress with it.skip or xit

Solution 7 - Javascript

My test files have a structure like this path/something.test.jsx and commands npx cypress run --spec path/something.test.jsx gives the following exception in the terminal:

Can't run because no spec files were found.
We searched for any files matching this glob pattern:
...

Surprisingly enough the following works and run the test exactly for one file (providing you have jest installed):

jest path/something.test.jsx

Solution 8 - Javascript

  1. A very easy solution is to prefix your tests in with numbers, as testing frameworks will typically will run tests in alpha/numeric order by default - so if I have to check one spec file - I will copy the contents into a file 0-[file-name].spec and re-run the test command. Once the test completes - you terminate the test run - as you will have the results you were looking for. This answer is targeted at projects where your testing framework is abstracted and as a developer, you do not have all available options for your testing framework. Not the best answer, but it works and is intuitive and super easy to do. I have found this to be a way to avoid adding a bunch of conditional skips() or only() calls that will not make it to production, will have to be removed and you can easily add the file pattern to .gitignore file so these local files do not get checked in.

Solution 9 - Javascript

To run a specific file through Terminal:

 npx cypress run --record --spec "cypress/integration/my-spec.js"

 npm run cypress -- --record --spec "cypress/integration/my-spec.js"

Solution 10 - Javascript

You can use this

cypress run -- --spec 'path/to/files/*.spec.js'

or

npm run --spec 'path/to/files/*.spec.js'

It worked for me.

Many thanks

Solution 11 - Javascript

use the @focus keyword in the test scripts when execute using cypress open

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionkucebView Question on Stackoverflow
Solution 1 - JavascriptkucebView Answer on Stackoverflow
Solution 2 - JavascriptMorlo MbakopView Answer on Stackoverflow
Solution 3 - JavascriptOleksandr TkalenkoView Answer on Stackoverflow
Solution 4 - JavascriptKevdog777View Answer on Stackoverflow
Solution 5 - JavascriptMarkoView Answer on Stackoverflow
Solution 6 - JavascriptUtkarsh JoshiView Answer on Stackoverflow
Solution 7 - JavascriptRomanView Answer on Stackoverflow
Solution 8 - JavascriptM4V3R1CKView Answer on Stackoverflow
Solution 9 - JavascriptGHULAM NABIView Answer on Stackoverflow
Solution 10 - JavascriptsaurabhshcsView Answer on Stackoverflow
Solution 11 - JavascriptThimiraRView Answer on Stackoverflow