Run Jest Watch Mode by default locally with is-ci-cli

In CI, we don’t want to start the tests in watch mode, but locally we normally want to run the tests in watch mode. We can have separate scripts, but it’d be great to not have to remember which script to run locally. Let’s use is-ci-cli to run the right script in the right environment when running the test script.

install:

npm i -D is-ci-cli

scripts:

    "test": "is-ci \"test:coverage\" \"test:watch\"",
"test:coverage": "jest --coverage",
"test:watch": "jest --watch",
"test:debug": "node --inspect-brk ./node_modules/jest/bin/jest.js --runInBand --watch",

So when we run:

npm t

It will check our enviorment, if it is running in CI mode, it will run coverage, otherwise it running in node, it runs watch mode.

Filter which Tests are Run with Typeahead Support in Jest Watch Mode

Jest’s watch mode is pluggable and jest-watch-typeahead is one plugin that you definitely don’t want to live without. It enhances the watch mode experience to help you know which tests will be run based on your filter. Making it even easier to run only the tests you’re concerned with running as you develop your codebase.

Install:

npm install --save-dev jest-watch-typeahead

jest.config.js:

const path = require('path');

module.exports = {
testEnvironment: 'jest-environment-jsdom', //'jest-environment-node',
moduleDirectories: [
'node_modules',
path.join(__dirname, 'src'),
'shared',
path.join(__dirname, 'test'),
],
moduleNameMapper: {
'\\.module\\.css$': 'identity-obj-proxy',
'\\.css$': require.resolve('./test/style-mock.js')
},
snapshotSerializers: ['jest-serializer-path'],
// after jest is loaded
setupTestFrameworkScriptFile: require.resolve('./test/setup-tests.js'),
collectCoverageFrom: ['**/src/**/*.js'],
coverageThreshold: {
global: {
statements: 80,
branchs: 80,
lines: 80,
functions: 80,
},
'./src/shared/utils.js': {
statements: 100,
branchs: 80,
lines: 100,
functions: 100,
}
},
watchPlugins: [
'jest-watch-typeahead/filename',
'jest-watch-typeahead/testname'
,
]
}

Run tests with a different configuration using Jest’s --config flag and testMatch option

Sometimes you may have situations where configuration needs to be different for certain tests. In this lesson we’ll take a look at how we could create a custom configuration for tests that are intended to run in a node environment.

We might want to test server side rendering code, which doesn't need DOM, and some other configurations for client side. For that we need to split current jest config, to need the requirements.

test/jest-common.js:

const path = require('path');

module.exports = {
rootDir: path.join(__dirname, '..'), // find tests in src folder
moduleDirectories: [
'node_modules',
path.join(__dirname, '../src'),
'shared',
__dirname,
],
moduleNameMapper: {
'\\.module\\.css$': 'identity-obj-proxy',
'\\.css$': require.resolve('./style-mock.js')
},
snapshotSerializers: ['jest-serializer-path'],
collectCoverageFrom: ['**/src/**/*.js'],
}

test/jest-client.js

module.exports = {
...require('./jest-common'),
testEnvironment: 'jest-environment-jsdom', //'jest-environment-node',
// after jest is loaded
setupTestFrameworkScriptFile: require.resolve('./setup-tests.js'),
coverageThreshold: {
global: {
statements: 80,
branchs: 80,
lines: 80,
functions: 80,
},
'./src/shared/utils.js': {
statements: 100,
branchs: 80,
lines: 100,
functions: 100,
}
},
watchPlugins: [
'jest-watch-typeahead/filename',
'jest-watch-typeahead/testname',
]
}

test/jest-server.js

const path = require('path')

module.exports = {
...require('./jest-common'),
coverageDirectory: path.join(__dirname, '../coverage/server'),
testEnvironment: 'jest-environment-node',
testMatch: ['**/__server_tests__/**/*.js']
}

With that we can create new script for running the jest:

    "test": "is-ci \"test:coverage\" \"test:watch:client\" # CI=1 npm t run in ci mode",
"test:coverage": "npm run test:coverage:client && npm run test:coverage:server",
"test:coverage:client": "jest --config test/jest-client.js --coverage",
"test:coverage:server": "jest --config test/jest-server.js --coverage",
"test:watch:client": "jest --config test/jest-client.js --watch",
"test:watch:server": "jest --config test/jest-server.js --watch",
"test:debug:client": "node --inspect-brk ./node_modules/jest/bin/jest.js --config test/jest-client.js --runInBand --watch",
"test:debug:server": "node --inspect-brk ./node_modules/jest/bin/jest.js --config test/jest-server.js --runInBand --watch",

The hightlighted code in script is how we run jest with the configuration file.

Support Running Multiple Configurations with Jest’s Projects Feature

Sometimes you may find it useful to have more than one configuration in a project (for example, running some tests in a node environment and others in the jsdom environment). In this lesson we’ll learn about Jest’s projects feature to have jest run both of these configurations at once.

Now we have lots of scripts for client and server:

    "test": "is-ci \"test:coverage\" \"test:watch:client\" # CI=1 npm t run in ci mode",
"test:coverage": "npm run test:coverage:client && npm run test:coverage:server",
"test:coverage:client": "jest --config test/jest-client.js --coverage",
"test:coverage:server": "jest --config test/jest-server.js --coverage",
"test:watch:client": "jest --config test/jest-client.js --watch",
"test:watch:server": "jest --config test/jest-server.js --watch",
"test:debug:client": "node --inspect-brk ./node_modules/jest/bin/jest.js --config test/jest-client.js --runInBand --watch",
"test:debug:server": "node --inspect-brk ./node_modules/jest/bin/jest.js --config test/jest-server.js --runInBand --watch",

Those are not ideal, in fact we prefer:

    "test": "is-ci \"test:coverage\" \"test:watch\"",
"test:coverage": "jest --coverage",
"test:watch": "jest --watch",
"test:debug": "node --inspect-brk ./node_modules/jest/bin/jest.js --runInBand --watch",

Jest provides '--projects' options we can use to run mutiplue scripts:

npx jest --projects ./test/jest-client.js ./test/jest-server.js

It runs based on both client config and server config.

Now we can config '--projects' inside jest.config.js:

/*Mainly for global jest config*/
// npx jest --showConifg --config ./test/jest-client.js
module.exports = {
...require('./test/jest-common'),
projects: ['./test/jest-client.js', './test/jest-server.js'],
coverageThreshold: {
global: {
statements: 80,
branchs: 80,
lines: 80,
functions: 80,
},
'./src/shared/utils.js': {
statements: 100,
branchs: 80,
lines: 100,
functions: 100,
}
},
collectCoverageFrom: ['**/src/**/*.js'],
}

Coverage reports will be combine by jest automaticlly for both client and server side.

./test/jest-clinet.js

module.exports = {
...require('./jest-common'),
displayName: 'dom',
testEnvironment: 'jest-environment-jsdom', //'jest-environment-node',
// after jest is loaded
setupTestFrameworkScriptFile: require.resolve('./setup-tests.js'),
watchPlugins: [
'jest-watch-typeahead/filename',
'jest-watch-typeahead/testname',
]
}

./test/jest-server.js:

const path = require('path')

module.exports = {
...require('./jest-common'),
displayName: 'server',
testEnvironment: 'jest-environment-node',
testMatch: ['**/__server_tests__/**/*.js']
}

./test/jest-common.js:

const path = require('path');

module.exports = {
rootDir: path.join(__dirname, '..'), // find tests in src folder
moduleDirectories: [
'node_modules',
path.join(__dirname, '../src'),
'shared',
__dirname,
],
moduleNameMapper: {
'\\.module\\.css$': 'identity-obj-proxy',
'\\.css$': require.resolve('./style-mock.js')
},
snapshotSerializers: ['jest-serializer-path'],
}

We added 'displayName':

So it is clear, tests are from which part.

If you just want run client test, you still can do:

npx jest --config ./test/jest-client.js --watch

Test specific projects in Jest Watch Mode with jest-watch-select-projects

It’s great that we can run multiple projects in our watch mode and that we can scope the tests down to specific tests, but sometimes it’s nice to be able to quickly switch between projects in watch mode. Let’s see how this works with jest-watch-select-projects.

After we refactor our scripts, now if we want to just run client tests, we need to do:

npx jest --config ./test/jest-client.js --watch

It is not so good approach.

Install:

npm i -D jest-watch-select-projects

In the 'watchPlugins':

  watchPlugins: [
'jest-watch-typeahead/filename',
'jest-watch-typeahead/testname',
'jest-watch-select-projects',
],

Now, if we run:

jest--watch

It will give a new options, which is 'P', we can select the project we want to run against.

Run ESLint with Jest using jest-runner-eslint

Jest is more than a testing framework. It’s a highly optimized, blazing fast platform with incredible parallelization for running tasks across many files in our project. It has a capability to run more than just tests. We can bring these features to our linting as well. Let’s see how we can bring our favorite Jest features (like watch mode) to ESLint with jest-runner-eslint.

Idea is using jest to run eslint as well though jest-runner

Install:

npm i -D jest-runner-eslint

Create test/jest-lint.js

const {rootDir} = require('./jest-common')

module.exports = {
rootDir,
displayName: 'lint',
runner: 'jest-runner-eslint',
testMatch: ['<rootDir>/**/*.js'],
testPathIgnorePatterns: ['/node_modules/', '/coverage/', '/dist/', '/other/']
}

To run the lint, we can do:

npx jest --config test/jest-lint.js

We want to include 'lint' into the default tests runner:

jest.config.js:

module.exports = {
...require('./test/jest-common'),
projects: ['./test/jest-lint.js', './test/jest-client.js', './test/jest-server.js'],
coverageThreshold: {
global: {
statements: 80,
branchs: 80,
lines: 80,
functions: 80,
},
'./src/shared/utils.js': {
statements: 100,
branchs: 80,
lines: 100,
functions: 100,
}
},
collectCoverageFrom: ['**/src/**/*.js'],
}

Now everytime, we run test, the lint will be also running.

Last, we can update our scripts to run the lint:

"lint": "jest --config test/jest-lint.js",

Run only relevant Jest tests on git commit to avoid breakages

Running the project tests on commit is a great way to avoid breaking the application accidentally and leverage the mechanism for confidence you have from your testbase. However, as the testbase grows this can take a very long time and slow productivity down. Let’s see how Jest is capable of running only the tests and linting only the files that are affected by the files we’re committing with husky and lint-staged to speed up our local test runs as well as help us avoid accidentally committing code that breaks our application.

You can target one file to run all the tests which are related:

npx jest --findRelatedTests src/shared/util.js

Install:

npm i -D husky lint-staged

Add lint-staged.config.js file:

module.exports = {
linters: {
'**/*.js': ['jest --findRelatedTests'] // any file which jest find related tests found will be added to the lint-staged
}
}

In package.json:

"precommit": "lint-staged",

Then if we were going to change one file and break the tests, then after we do git commit, husky will kick in and run the tests which are related to the file we have changed. If the tests faild, we are not able to commit the code.

[Testing] Config jest to test Javascript Application -- Part 3的更多相关文章

  1. [Testing] Config jest to test Javascript Application -- Part 1

    Transpile Modules with Babel in Jest Tests Jest automatically loads and applies our babel configurat ...

  2. [Testing] Config jest to test Javascript Application -- Part 2

    Setup an afterEach Test Hook for all tests with Jest setupTestFrameworkScriptFile With our current t ...

  3. Web.config Transformation Syntax for Web Application Project Deployment

    Web.config Transformation Syntax for Web Application Project Deployment Other Versions   Updated: Ma ...

  4. JavaScript Application Architecture On The Road To 2015

    JavaScript Application Architecture On The Road To 2015 I once told someone I was an architect. It’s ...

  5. 转:Transform Web.Config when Deploying a Web Application Project

    Introduction One of the really cool features that are integrated with Visual Studio 2010 is Web.Conf ...

  6. spring cloud config的bootstrap.yml与application.proterties的区别

    bootstrap.yml  和application.yml  都可以用来配置参数 bootstrap.yml可以理解成系统级别的一些参数配置,这些参数一般是不会变动的 application.ym ...

  7. Unit Testing a zend-mvc application

    Unit Testing a zend-mvc application A solid unit test suite is essential for ongoing development in ...

  8. JavaScript Web Application summary

    Widget/ HTML DOM (CORE) (local dom) DOM, BOM, Event(Framework, UI, Widget) function(closure) DATA (c ...

  9. JavaScript Libraries In A TypeScript Application, Revisited

    If you haven’t already gotten involved with it, you’ll probably know that TypeScript is becoming inc ...

随机推荐

  1. python:mysql增量备份

    模块:MySQLdb Crypto加密 ConfigParser加载配置 mydb.py #!/usr/bin/env python #coding=utf-8 import MySQLdb as m ...

  2. RN笔记

    https://facebook.github.io/react-native/docs/using-a-listview.html react native类似于react,不过它使用的是原生组件, ...

  3. 爬虫练习四:爬取b站番剧字幕

    由于个人经常在空闲时间在b站看些小视频欢乐一下,这次就想到了爬取b站视频的弹幕. 这里就以番剧<我的妹妹不可能那么可爱>第一季为例,抓取这一番剧每一话对应的弹幕. 1. 分析页面 这部番剧 ...

  4. Python学习网站推荐

    B站是目前本人看到的最好的免费学习Python的网站 黑马程序员- https://space.bilibili.com/37974444?spm_id_from=333.338.viewbox_re ...

  5. wordcloud的安装报错 error: Microsoft Visual C++ 10.0 is required. Get it with "Microsoft Windows SDK 7.1"解决办法

    cmd中使用pip install wordcloud失败,没看懂报错的原因…… 而在pycharm中添加也报错 解决方法: 1. 下载wordcloud-1.4.1.tar.gz,解压缩 cmd c ...

  6. 基础训练 2n皇后问题

    2n皇后问题 #include<iostream> #include<vector> using namespace std; int cnt = 0, n; vector&l ...

  7. LeetCode 653. Two Sum IV – Input is a BST

    Given a Binary Search Tree and a target number, return true if there exist two elements in the BST s ...

  8. 算法学习记录-图——最小生成树之prim算法

    一个连通图的生成树是一个极小的连通子图,它包含图中全部的顶点(n个顶点),但只有n-1条边. 最小生成树:构造连通网的最小代价(最小权值)生成树. prim算法在严蔚敏树上有解释,但是都是数学语言,很 ...

  9. Python paramiko模块 + 堡垒机

    paremiko SSHClient 用于连接远程服务器并执行基本命令 基于用户名密码连接: import paramiko    # 创建SSH对象 ssh = paramiko.SSHClient ...

  10. wordpress无法登录的解决方法

    使用wordpress建站的朋友可能会遇到wordpress管理密码,有时甚至是正确的密码,但是多次尝试输入都无法登录,并且输入用户名和输入电子邮件都无法获取密码,遇到这种情况怎么办,本文教你如何处理 ...