The jest-function uses js2, so it does not work on other modes like typescript-mode.

A few ideas:

• one option could be to just add code to get the same information from other modes.
• another one could be to have some basic heuristics and not rely on js2-mode at all. So using some basic regular expressions to extract the path of describe/it strings.
• Maybe another libraries like like lsp, imenu, could be used?

Line: 385 python-pdbtrack-comint-output-filter-function

      (when jest-pdb-track
        (add-hook
         'comint-output-filter-functions
         'python-pdbtrack-comint-output-filter-function
         nil t))

The code only requires

(require 'comint)
(require 'compile)
(require 'js2-mode)

(require 'dash)
(require 'dash-functional)
(require 'magit-popup)
(require 'projectile)

Which probably don't contain python-pdbtrack-comint-output-filter-function

When jest--current-defun finds a function jest is called with a command line like jest file.test.js::functionName. To my understanding the :: syntax is unknown to jest so matching tests will never be found. jest --testNamePattern=<regex> should be used instead.

Is there a way to make the jest output buffer clear its contents before running the tests again?

Running jest-file against a test file works as expected, but only once. If the compilation buffer exists, subsequently running jest-file does not result in the tests being run. The *Messages* buffer simply contains jest--run-as-comint: Text is read-only.

I've been trying to use your package without good results, for the installation I'm using use-package in this way:

;; Jest mode
(use-package jest
  :ensure t
  :config
  (setq jest-executable "npm run test --"))

(use-package add-node-modules-path
  :ensure t)

When I'm editing a test file and after executing M-x jest-popup t I get the following message in the minibuffer:

Wrong type argument: stringp, nil

My package.json looks like this:

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

Could anyone provide me help on this configuration issue?

Introduce in #22 but I have no idea how to run them.

When trying to run any jest- function I get the following error:
Symbol's function definition is void: s-prefix-p

I'm running emacs 26.2

I have been setting up jest.el for my projects and noticed that the default value of jest-executable (npm test) is not that general.

In my case, the default breaks because we work in a monorepository where the toplevel test is not directly invoking jest.

Proposed solution

I would propose to change it to npx --no-install jest, which should work in a larger number of cases.

The downside is you need a bit more modern version of npm. But it was introduced a while back.

Alternative solution

Alternatively, finding "jest" in the path would also work and the user could rely on add-node-modules-path. Related discussion: #2. But my proposed default value should work in most installations.

I was excited to use emacs-jest, but when I tried it out I got:
/bin/sh jest: command not found.

Could it be possible to make it so that this package looks for jest in the module? Like it could try to find the nearest package.json and execute jest from the node_modules in that folder.

I've used other packages like grunt.el https://github.com/gempesaw/grunt.el and it has similar behavior where it tries to find the nearest package json to run grunt.

Any reason why colors are disabled by default and would you be amenable to adding an option to enable them by default?

Hi,

Is it possible to set the jest test buffer to readonly by default?

Thanks :)

There are a few thing that are left over from the pytest pilfering such as

-d run doctest (--doctest-modules)

That need to be removed.

Hi!

I have to use

  :config (require 'cc-defs)

in my use-package declaration of jest. Otherwise, I get invalid function c-int-to-char errors when testing single functions.

PR #29 is a basic implementation that seems to fix this.

For me some of the rules for java (and cucumber) were matching but they didn't do the right thing. It's conceivable that other people had some magic rules in compilation-error-regexp-alist from another language that worked for them...

Activating compilation-shell-minor-mode will enable the all the cool features of compilation-mode, for example, compilation-next-error, compilation-previous-error, and compile-goto-error. So you quickly go to a failing test and jump from its stack trace directly to the failed assertion.

My project does not store the Jest configuration in the project root. It stores the Jest configuration in web/react, where the relevant code lives. This directory includes files such as:

• jest.config.js
• package.json

Other project directories include code in other programming languages. There is no package.json in project/ or project/web.

#2 discusses the difficulty in finding the jest executable, but even if I hardcode a working executable, when I try to invoke jest-file on /Users/thomaswhaples/code/project/web/react/src/ReactAppName/SubApp/Component/__tests__/Form.spec.jsx

then the process runs in /Users/thomaswhaples/code/project instead of /Users/thomaswhaples/code/project/web/react. As a result, I have to hardcode an additional paramter:

--config web/react/package.json

This is inconvenient to set up, glues the configuration to one specific project, and generally should not be necessary.

For example, at work we have different jest config files for different repos. Because jest-arguments is global, when I save a config file for a particular repo, it is not only the default for that repo but also for other repos.