Execute Jest tests exclusively on the directory you are currently in

Question

Execute Jest tests exclusively on the directory you are currently in

When I run Jest on my machine by typing jest from the terminal, it automatically executes tests from parent folders as well. However, I want to only run tests from the current folder.

For example, if I navigate to c:/dev/app in the terminal and enter a command like some-jest-command, I expect it to only run files with the .test.js extension present in the app folder. Currently, running the jest command from the app folder includes tests from parent folders, which is not what I want.

javascript npm jestjs

Answer 1

Answer №1

To execute tests from a specific directory, utilize the --testPathPattern jest flag. Ensure to include the folder path when setting up the npm script. Add the flag in your npm scripts within package.json as shown below:

"scripts": {
    ....
    "test:unit": "jest --testPathPattern=src/js/tests/unit-tests",
    "test:integration": "jest  --testPathPattern=src/js/tests/integration"       
    ....
},

If you want to monitor for changes as well, add the watch flag:

{
  ...
  "test:unit": "jest --watch --testPathPattern=src/js/tests/unit-tests",
  ...
}

Once set up, navigate to the command line, switch to your project directory, and run either the unit test:

npm run test:unit

or integration tests:

npm run test:integration

Answer 2

To execute tests from a specific directory, utilize the --testPathPattern jest flag. Ensure to include the folder path when setting up the npm script. Add the flag in your npm scripts within package.json as shown below:

"scripts": {
    ....
    "test:unit": "jest --testPathPattern=src/js/tests/unit-tests",
    "test:integration": "jest  --testPathPattern=src/js/tests/integration"       
    ....
},

If you want to monitor for changes as well, add the watch flag:

{
  ...
  "test:unit": "jest --watch --testPathPattern=src/js/tests/unit-tests",
  ...
}

Once set up, navigate to the command line, switch to your project directory, and run either the unit test:

npm run test:unit

or integration tests:

npm run test:integration

Answer 3

Answer №2

By default, Jest will automatically test all files in the directory where the package.json file is located.

For example, if your project is in the folder c:/dev/app and your package.json is in c:, running the command npm test will run tests recursively starting from c:. To focus on specific folders like c:/dev/app, you can use the command npm test dev/app.

Answer 4

By default, Jest will automatically test all files in the directory where the package.json file is located.

For example, if your project is in the folder c:/dev/app and your package.json is in c:, running the command npm test will run tests recursively starting from c:. To focus on specific folders like c:/dev/app, you can use the command npm test dev/app.

Answer 5

Answer №3

If you want to restrict Jest testing to a specific directory and specify the type of files to be read (for example: 'ExampleComponent.test.js' with Jest version @24.9.0), you need to define the exact "testMatch" in your jest.config.json or package.json under the "jest" section like this

"testMatch": [ "<rootDir>/src/__tests/**/*.test.js" ]

. In my scenario, this testMatch pattern targets all files starting with .test.js in tests subdirectories while ignoring other files like 'setupTest.js' and other .js files in the 'mocks' subdirectory located within the 'tests' directory, hence my 'jest.config.json' appears as follows

    {
        "setupFiles": [
            "raf/polyfill",
            "<rootDir>/setupTests.js"
        ],
        "snapshotSerializers": [
            "enzyme-to-json/serializer"
        ],
        "moduleNameMapper": {
            "^.+\\.(css|less|scss|sass)$": "identity-obj-proxy"
        },
        "testMatch": [
            "<rootDir>/src/__tests/**/*.test.js"
        ]
    }

You can adjust the regular expression used for 'testMatch' according to your requirements.

Just a side note: This is applicable for [email protected] && [email protected] if it's relevant to anyone.

I trust that this information will prove helpful to someone, best wishes to all.

Answer 6

If you want to restrict Jest testing to a specific directory and specify the type of files to be read (for example: 'ExampleComponent.test.js' with Jest version @24.9.0), you need to define the exact "testMatch" in your jest.config.json or package.json under the "jest" section like this

"testMatch": [ "<rootDir>/src/__tests/**/*.test.js" ]

. In my scenario, this testMatch pattern targets all files starting with .test.js in tests subdirectories while ignoring other files like 'setupTest.js' and other .js files in the 'mocks' subdirectory located within the 'tests' directory, hence my 'jest.config.json' appears as follows

    {
        "setupFiles": [
            "raf/polyfill",
            "<rootDir>/setupTests.js"
        ],
        "snapshotSerializers": [
            "enzyme-to-json/serializer"
        ],
        "moduleNameMapper": {
            "^.+\\.(css|less|scss|sass)$": "identity-obj-proxy"
        },
        "testMatch": [
            "<rootDir>/src/__tests/**/*.test.js"
        ]
    }

You can adjust the regular expression used for 'testMatch' according to your requirements.

Just a side note: This is applicable for [email protected] && [email protected] if it's relevant to anyone.

I trust that this information will prove helpful to someone, best wishes to all.

Answer 7

Answer №4

To execute tests for specific files in your project, navigate to the root directory and use the command jest <substring of files>. This will run only the test files that contain the specified substring.

$ jest /libs/components
> [PASS] /libs/components/button.tsx

Answer 8

To execute tests for specific files in your project, navigate to the root directory and use the command jest <substring of files>. This will run only the test files that contain the specified substring.

$ jest /libs/components
> [PASS] /libs/components/button.tsx

Answer 9

Answer №5

--package.json

"scripts": {
    "test": "jest"
  }

--jest.config.js

module.exports = {
    "testMatch": [
        "<rootDir>/tests/unit/*.test.js"
    ]
  }

Answer 10

--package.json

"scripts": {
    "test": "jest"
  }

--jest.config.js

module.exports = {
    "testMatch": [
        "<rootDir>/tests/unit/*.test.js"
    ]
  }

Answer 11

Answer №6

Testing instructions:

To test a specific folder, use the following commands:

yarn:

yarn test nameoffolder

npm:

npm test nameoffolder

For instance, if you have a directory called widget and wish to only run tests within the widget folder, execute this command.

yarn:

yarn test widget

npm:

npm test widget

Answer 12

Testing instructions:

To test a specific folder, use the following commands:

yarn:

yarn test nameoffolder

npm:

npm test nameoffolder

For instance, if you have a directory called widget and wish to only run tests within the widget folder, execute this command.

yarn:

yarn test widget

npm:

npm test widget

Answer 13

Answer №7

If you want to focus on a specific section within a test file, you can use the -t option when running jest as long as that section has a unique describe statement.

For example, let's say we have the following test file:

...

describe('specific section XYZ', () => {
    it('test A', () => { ... });
    it('test B', () => { ... });
    it('test C', () => { ... });
    it('test D', () => { ... });
});

...

To run only the tests within the "specific section XYZ", you can use this command:

jest -t "specific section XYZ"

.

Here is an explanation of the -t flag:

-t, --testNamePattern        Run only tests with a name that matches the regex pattern.

Answer 14

If you want to focus on a specific section within a test file, you can use the -t option when running jest as long as that section has a unique describe statement.

For example, let's say we have the following test file:

...

describe('specific section XYZ', () => {
    it('test A', () => { ... });
    it('test B', () => { ... });
    it('test C', () => { ... });
    it('test D', () => { ... });
});

...

To run only the tests within the "specific section XYZ", you can use this command:

jest -t "specific section XYZ"

.

Here is an explanation of the -t flag:

-t, --testNamePattern        Run only tests with a name that matches the regex pattern.

Answer 15

Answer №8

Suppose you are currently in the directory path /project/homepage; to run only the tests within the homepage/ directory using jest, do the following:

npx jest --watch homepage

If typing the directory name is a hassle, utilize the subshell command $(basename "$PWD"), as shown below:

npx jest --watch $(basename "$PWD")

The command $(basename "$PWD") extracts the base name of the current working directory ($PWD).
- The basename function removes the directory path and retains only the final component (i.e., the directory name itself, such as homepage from /project/homepage).

Answer 16

Suppose you are currently in the directory path /project/homepage; to run only the tests within the homepage/ directory using jest, do the following:

npx jest --watch homepage

If typing the directory name is a hassle, utilize the subshell command $(basename "$PWD"), as shown below:

npx jest --watch $(basename "$PWD")

The command $(basename "$PWD") extracts the base name of the current working directory ($PWD).
- The basename function removes the directory path and retains only the final component (i.e., the directory name itself, such as homepage from /project/homepage).

Execute Jest tests exclusively on the directory you are currently in

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Answer №6

Answer №7

Answer №8

Similar questions

Error message in Angular 2, Problem found in inline template while utilizing eval() function

Animation effect in Jquery failing to execute properly within a Modal

Displaying dates in Meteor Handlebars using `{{ timestamp }}` braces

What is the process for creating an index signature for a type alias representing a Map in Typescript?

Updating the image source using Javascript

"Maintaining Consistency: Ensuring The First Row is Repeated on Every

Creating a TypeScript shell command that can be installed globally and used portably

Show live updates in the input field

Need help implementing the disableGutters property on MTableToolbar?

The error message "gulp error - _.flattenDeep is not a function when using gulp.watch" is indicating

Leveraging current state data (from store) in ReactJS promptly

Issue with loading HTML file correctly in Django

Using three.js to create a rotating analog clock in Javascript

Browser encountering HTTP response that has been shorted extensively

Using Express and React with Socket.io

Is there a way to show a loading indicator while waiting for ajax to finish loading?

Is it possible for links to remain clickable even if they pass underneath a div

Making a Dialog resizable with jQuery's Resizable Helper

"Trouble with Express.js: CSS isn't loading, yet HTML displays

Guide to verifying all chosen options in a multiple select field using EJS