I have a Node.js app using TypeScript and now I want Jasmine to run tests automatically each time I make changes in .ts files. So I'm just trying to find an appropriate mand to be run as npm test in mand line or a package that can watch my .ts files pile them on changes and run jasmine. Does anybody know a solution for it?

I have a Node.js app using TypeScript and now I want Jasmine to run tests automatically each time I make changes in .ts files. So I'm just trying to find an appropriate mand to be run as npm test in mand line or a package that can watch my .ts files pile them on changes and run jasmine. Does anybody know a solution for it?

• javascript
• node.js
• typescript
• jasmine

• What is your current test mand? IE, in your package.json, what is test in the scripts block? – Matt Morgan Commented Feb 1, 2018 at 19:22

4 Answers 4

The easiest way I found is

installing dependencies: npm install --save-dev jasmine-ts nodemon

initializing jasmine: node_modules/.bin/jasmine-ts init

In the package.json:

"scripts": {
    "test": "nodemon --ext ts --exec 'jasmine-ts \"src/**/*.spec.ts\"'"
}

Edit: the above solution doesn't work as of the 11th of Apr, 2019. I published a modified working example at https://github./erosb/ts-node-jasmine-example

This may be done with two mands launched in separate terminals. Assuming packages are installed in global mode.

First mand launches TypeScript piler in watch mode:

tsc --watch

The second starts nodemon that watches .js files and restarts on changes. Each time it executes jasmine test runner:

nodemon --ext js --exec 'jasmine JASMINE_CONFIG_PATH=jasmine.json'

This solution is fast enough though it also has a drawback of running in two terminals. So it is not ideal but the best I've found so far.

As a result scripts section in package.json looks like:

"scripts": {
  /* ... */
  "watch": "tsc --watch",
  "test": "nodemon --ext js --exec 'jasmine JASMINE_CONFIG_PATH=jasmine.json'",
  "devstart": "nodemon ./bin/www"
},

devstart also works in couple with watch restarting server each time .ts files are changed (after they are piled to .js).

Previously described methods either did not work, or were slow to pile code. Here is my attempt to solve this, both fast and convenient, works great for me. The only downside is that jasmine would not know which tests are affected by TS repilation and would run all the tests.

yarn add tsc-watch --dev

yarn run tsc-watch --onSuccess "yarn run jasmine --config=jasmine.json"

NPM version:

npm -i tsc-watch

npm run tsc-watch --onSuccess "npm run jasmine --config=jasmine.json"

In my case I needed to correctly map TS paths. The full mand looks like this:

yarn run tsc-watch --onSuccess \
     "node -r tsconfig-paths/register node_modules/jasmine/bin/jasmine \
     --config=jest/jasmine.json --require=dist/jest/setup.js $targetFile"

jasmine.json

{
  "spec_dir": "dist/src",
  "spec_files": ["**/*.e2e.js", "**/*.unit.js", "**/*.spec.js", "**/*.test.js"],
  "env": {
    "random": false
  }
}

Just an example, please adjust to your needs.

tsc-watch starts a TypeScript piler with --watch parameter, with the ability to react to successful pilation and start tests.

You might consider using jasmine-node. I don't think that jasmine itself has a watch option.

npm i -g jasmine-node

Assuming that your test mand in your package.json scripts block is something like this:

"scripts": {
    ...
    "test": "jasmine some-directory-or-glob-pattern"
    ...
}

Use jasmine-node and add the --autotest and --watch flags to that mand:

"scripts": {
    ...
    "test": "jasmine-node --autotest --watch some-directory-or-glob-pattern"
    ...
}