ci: use different jest settings for production and development envs

This allows to test in CI the same compiled version of library as used
by other apps in production, while testing TypeScript sources only in
development mode.

Author: tsufiev

jest.config.js renamed to jest.config.development.js

@@ -0,0 +1,5 @@
+module.exports = {
+    roots: ['<rootDir>/build/cjs'],
+    testRegex: '(/__tests__/.*|(\\.|/)(test|spec))\\.js$',
+    moduleFileExtensions: ['js', 'jsx', 'json', 'node'],
+}

jest.config.production.js

@@ -16,8 +16,9 @@
   ],
   "scripts": {
     "test:unit": "exit 0",
-    "test:integration": "jest",
-    "test:all": "run-p test:unit test:integration",
+    "test:integration:development": "TEST_ENVIRONMENT=dev jest --config jest.config.development.js",
+    "test:integration:production": "jest --config jest.config.production.js",
+    "test:all": "run-p test:unit test:integration:production",
     "test": "npm run test:unit",
     "build": "tsc -p tsconfig-esm.json && tsc -p tsconfig-cjs.json && ./fixup.sh",
     "clean": "rm -rf build",

package.json

@@ -1,4 +1,5 @@
-const pkgInfo = require('../package.json');
+const pkgPath = process.env.TEST_ENVIRONMENT === 'dev' ? '../package.json' : '../../package.json';
+const pkgInfo = require(pkgPath);
 
 function getVersion() {
     return pkgInfo.version;