Yes, you can set a custom environment for a single Jest test using the docblock syntax.

If your custom environment is installed as a package in node_modules you can just use the module name.

Alternatively, if your custom environment is defined in a file within your project you can use the path to that file (in this case my-custom-env.js in the root directory of the project):

/**
 * @jest-environment ./my-custom-env
 */

In my case, the solution was:

• Install this package: jest-environment-jsdom
• Add testEnvironment: 'jest-environment-jsdom' into my jest.config.js;
• Run yarn test (my script: "test": "jest --verbose")

You can see better bellow or the file here in repository ShareBookBR/sharebook-frontend-next

module.exports = {
    setupFilesAfterEnv: ['<rootDir>/jest.setup.ts'],
    testPathIgnorePatterns: ['<rootDir>/.next/', '<rootDir>/node_modules/'],
    moduleNameMapper: {
        //To include new paths, include also into tsconfig.paths.json
        '\\.(scss|sass|css)$': 'identity-obj-proxy',
        // '^@/sharebook-components/(.*)$': '<rootDir>/components/$1', //to all paths, ex: @sharebook-components/somegfolder
        '^@sharebook-themes': '<rootDir>/src/themes',
        '^@sharebook-layouts': '<rootDir>/src/layouts',
        '^@sharebook-components': '<rootDir>/src/components',
        '^@sharebook-hooks': '<rootDir>/src/hooks',
        '^@sharebook-configs': '<rootDir>/src/configs',
        '^@sharebook-axios': '<rootDir>/src/axios',
        '^@sharebook-utils': '<rootDir>/src/utils'
    },
    testEnvironment: 'jest-environment-jsdom'
};