curben
/
blog
mirror of https://gitlab.com/curben/blog
1
0
Fork 0
Code Issues Releases Wiki Activity

post(jest): no longer use module-export to declare config 

- ce8c4a145b
This commit is contained in:
MDLeom 2020-09-28 05:52:42 +00:00
parent c6d0369b95
commit 9cc697b937
No known key found for this signature in database
GPG Key ID: 32D3E28E96A695E8
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
source/_posts/unit-testing-jest.md
View File

@ -2,6 +2,7 @@
title: Javascript Unit Testing with Jest title: Javascript Unit Testing with Jest
excerpt: Jest = Chai + Mocha + NYC + Sinon excerpt: Jest = Chai + Mocha + NYC + Sinon
date: 2019-12-30 date: 2019-12-30
updated: 2020-09-28
tags: tags:
- javascript - javascript
--- ---
@ -36,7 +37,9 @@ Since it's only three lines and I prefer to minimise the files, I moved the conf
Now, hexo-yam has many defaults to maximise the compressions. I prefer not to repeat the same config in the unit test, so I declared them as objects and module-export. Now, hexo-yam has many defaults to maximise the compressions. I prefer not to repeat the same config in the unit test, so I declared them as objects and module-export.
``` js Edit (28 Sep 2020): I now find using module-export simply for the purpose of unit testing to be a bit _unhygienic_, so I no longer use this approach, now default config is declared in each test instead.
``` js index.js
// the actual object has many properties, this is just a preview // the actual object has many properties, this is just a preview
const htmlDefault = { const htmlDefault = {
minifyJS: true, minifyJS: true,
@ -52,7 +55,7 @@ module.exports = {
Then in the test, I simply import `htmlDefault` object, Then in the test, I simply import `htmlDefault` object,
``` js ``` js test/html.test.js
describe('html', () => { describe('html', () => {
const { htmlDefault } = require('../index') const { htmlDefault } = require('../index')
@ -134,7 +137,7 @@ expect(result).toEqual(expect.not.arrayContaining(expected))
When `verbose:` option is enabled, the plugin would output `${feature}: {path} [${percentage}% saved]` to stdout using `hexo.log.log()`. The percentage is the size difference between the original and minified file. When `verbose:` option is enabled, the plugin would output `${feature}: {path} [${percentage}% saved]` to stdout using `hexo.log.log()`. The percentage is the size difference between the original and minified file.
For example: Example output:
``` ```
html: foo/bar/baz.html [10.10% saved] html: foo/bar/baz.html [10.10% saved]
@ -159,7 +162,7 @@ Initially I tested it by using [`.toHaveBeenCalledWith(arg)`](https://jestjs.io/
expect(hexo.log.log).toHaveBeenCalledWith(`html: foo/bar/baz.html [10.10% saved]`); expect(hexo.log.log).toHaveBeenCalledWith(`html: foo/bar/baz.html [10.10% saved]`);
``` ```
Then I realized the percentage could change as upstream minifiers get enhanced or even regressed. However, since the test input is just a line of code, it's practically impossible that the percentage will change. Yet, not taking chances to be safe. So, I refactored it into, Then I realized the percentage could change as upstream minifiers get enhanced or even regressed. However, since the test input is just a line of code, it's practically impossible that the percentage will change. Yet, to be safe, I skip checking the percentage,
``` js ``` js
expect(hexo.log.log.mock.calls[0][0]).toContain('html: foo/bar/baz.html') expect(hexo.log.log.mock.calls[0][0]).toContain('html: foo/bar/baz.html')