Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create empty mocks for jest #303

Merged
merged 19 commits into from
May 19, 2018
Merged

Create empty mocks for jest #303

Show file tree
Hide file tree
Changes from 6 commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
354c659
Add postinstall script for creating mocks
May 10, 2018
ba4efdf
Add new lines at the end
May 10, 2018
54be94d
Update postinstall script to add setupAppCenter.js file and to update…
May 10, 2018
7cdca52
Return if we can not find package.json
May 10, 2018
df4ee9b
Fix eslint errors
May 10, 2018
980045d
Fix eslint errors and modify eslint.rc in test apps
May 10, 2018
16a29bd
Reimplement mocking with js modules mocks
May 14, 2018
5d62992
Add AppCenter mocks to TestApp
May 14, 2018
c56d4f0
Check if jest is present as dependency
May 15, 2018
ba562fc
Fix indentation
May 15, 2018
12c0b91
Separate mocks added to appcenter modules
May 17, 2018
bfd5a94
Postinstall script in modules updated to modify package.json
May 17, 2018
7431b3d
Update TestApp package.json
May 17, 2018
e38e7df
Extract common code to link-scripts module
May 18, 2018
7cf3956
Rename mock files
May 18, 2018
6222c6e
Add js extension for require
May 18, 2018
688e28e
Update link-scripts path in postinstall
May 18, 2018
fe3fdc3
Move setup mock script to appcenter module
May 18, 2018
91565da
Remove mocks from TestApp
May 18, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion TestApp/.eslintrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
{
"parser": "babel-eslint",
"env": {
"es6": true
"es6": true,
"jest": true
},
"plugins": [
"react"
Expand Down
3 changes: 2 additions & 1 deletion TestApp34/.eslintrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
{
"parser": "babel-eslint",
"env": {
"es6": true
"es6": true,
"jest": true
},
"plugins": [
"react"
Expand Down
3 changes: 2 additions & 1 deletion appcenter-crashes/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,7 @@
"eslint-plugin-react": "^7.2.1"
},
"scripts": {
"lint": "./node_modules/.bin/eslint ."
"lint": "./node_modules/.bin/eslint .",
"postinstall": "node scripts/postinstall"
}
}
50 changes: 50 additions & 0 deletions appcenter-crashes/scripts/postinstall.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
const fs = require('fs');
const path = require('path');

const projectDirectory = path.resolve(`${__dirname}${path.sep}..${path.sep}..${path.sep}..`);
const testDirectory = path.join(projectDirectory, 'test');
Copy link

@atticoos atticoos May 11, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is overall a really interesting solution, and it'd be wonderful if there was an established standard in providing mocks to dependents.

Anyway, this assume's the dependent's directory structure, and overall doesn't feel right to "inject" source files into a dependent, versus link to them

What if the mocks lived in a file here, and you just link to that in projectJson.jest.setupFiles?

Eg:

packageJson.jest.setupFiles.push('node_modules/appcenter-crashes/jest/mocks.js')

const setupFileName = 'setupAppCenter.js';
const packageJsonFile = path.join(`${projectDirectory}`, 'package.json');

// Update project.json
let packageJsonContent;
try {
packageJsonContent = fs.readFileSync(packageJsonFile, 'utf8');
} catch (e) {
console.log('Could not read package.json file');
return;
}
const projectJson = JSON.parse(packageJsonContent);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit - is there a reason to name this variable "projectJson" not "packageJson"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a typo, thanks!

if (Object.prototype.hasOwnProperty.call(projectJson, 'jest')) {
const setupFileNameValue = `.${path.sep}test${path.sep}${setupFileName}`;
if (projectJson.jest.setupFiles === undefined) {
projectJson.jest.setupFiles = [setupFileNameValue];
} else if (projectJson.jest.setupFiles.indexOf(setupFileNameValue) === -1) {
projectJson.jest.setupFiles.push(setupFileNameValue);
}
fs.writeFileSync(packageJsonFile, JSON.stringify(projectJson));
}

// Create setup mock file for Jest
if (!fs.existsSync(testDirectory)) {
fs.mkdirSync(testDirectory);
}

fs.writeFileSync(`${testDirectory}/${setupFileName}`, `
jest.mock('NativeModules', () => ({
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does jest.mock handle the scenario where the user has already defined a mock for NativeModules? Does this override/conflict with that? Or simply merge them?

AppCenterReactNativeCrashes: {
generateTestCrash: jest.fn(),
hasCrashedInLastSession: jest.fn(),
lastSessionCrashReport: jest.fn(),
isEnabled: jest.fn(),
setEnabled: jest.fn(),
notifyUserConfirmation: jest.fn(),
setListener: jest.fn()
},
AppCenterReactNativePush: {
setEnabled: jest.fn(),
isEnabled: jest.fn(),
setListener: jest.fn()
}
}));
`);
3 changes: 2 additions & 1 deletion appcenter-push/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@
"eslint-plugin-react": "^7.2.1"
},
"scripts": {
"lint": "./node_modules/.bin/eslint ."
"lint": "./node_modules/.bin/eslint .",
"postinstall": "node scripts/postinstall"
}
}
50 changes: 50 additions & 0 deletions appcenter-push/scripts/postinstall.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
const fs = require('fs');
const path = require('path');

const projectDirectory = path.resolve(`${__dirname}${path.sep}..${path.sep}..${path.sep}..`);
const testDirectory = path.join(projectDirectory, 'test');
const setupFileName = 'setupAppCenter.js';
const packageJsonFile = path.join(`${projectDirectory}`, 'package.json');
Copy link
Member

@guperrot guperrot May 17, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approach seems ok now based on latest discussion.

However this is duplicated code, we can put shared script code in the linker, I mean the core package and use it here.


// Update project.json
let packageJsonContent;
try {
packageJsonContent = fs.readFileSync(packageJsonFile, 'utf8');
} catch (e) {
console.log('Could not read package.json file');
return;
}
const projectJson = JSON.parse(packageJsonContent);
if (Object.prototype.hasOwnProperty.call(projectJson, 'jest')) {
const setupFileNameValue = `.${path.sep}test${path.sep}${setupFileName}`;
if (projectJson.jest.setupFiles === undefined) {
projectJson.jest.setupFiles = [setupFileNameValue];
} else if (projectJson.jest.setupFiles.indexOf(setupFileNameValue) === -1) {
projectJson.jest.setupFiles.push(setupFileNameValue);
}
fs.writeFileSync(packageJsonFile, JSON.stringify(projectJson));
}

// Create setup mock file for Jest
if (!fs.existsSync(testDirectory)) {
fs.mkdirSync(testDirectory);
}

fs.writeFileSync(`${testDirectory}/${setupFileName}`, `
jest.mock('NativeModules', () => ({
AppCenterReactNativeCrashes: {
generateTestCrash: jest.fn(),
hasCrashedInLastSession: jest.fn(),
lastSessionCrashReport: jest.fn(),
isEnabled: jest.fn(),
setEnabled: jest.fn(),
notifyUserConfirmation: jest.fn(),
setListener: jest.fn()
},
AppCenterReactNativePush: {
setEnabled: jest.fn(),
isEnabled: jest.fn(),
setListener: jest.fn()
}
}));
`);