WIP ⚠ configure jest with enzyme

[rady-ben]

• add new jest config
• add enzyme config
• test the render of the FileForm component

---

This change is 

[ancientTexts-net]

TODO: discuss with the team:
Seems like a helpful idea to verify prop-types on PUBLIC libraries.

[ancientTexts-net]

NOTE: there were a few missing proptypes 👍

[ancientTexts-net]

---

jest.enzyme.config.js, line 1 at r1 (raw file):

module.exports = {

For now, I think there is a different config for these "new" tests.

If this PR is going to be approved, we can probably refactor a single jest.config.js and

[ancientTexts-net]

---

package.json, line 32 at r1 (raw file):

    "test:unit": "NODE_ENV=test jest ./src/core --coverage && cat ./coverage/lcov.info | coveralls",
    "test": "nyc --exclude-after-remap=false npm run test:e2e",
    "testJestEnzyme": "jest --watch -c ./jest.enzyme.config.js",

For now, there are two ways to invoke jest.

But if this PR is going to be approved, maybe we can refactor into a single (combined) script

[ancientTexts-net]

---

mocks/fileMock.js, line 1 at r1 (raw file):

module.exports = 'test-file-stub';

see identity-obj-proxy 👍

[ancientTexts-net]

---

src/components/file/FileForm.js, line 22 at r1 (raw file):

    <Paper 
      style={{ marginBottom: '1em', padding: '1.3em' }}
      data-test="component-fileForm"

Several data-test elements added. 👍

[ancientTexts-net]

---

mocks/FileForm.test.js, line 27 at r1 (raw file):

const findByAttribute = (wrapper, attribute) => wrapper.find(`[data-test='${attribute}']`)

// render tests

TODO: can we look at these tests?

They look helpful to me.

• is this a good pattern for tests in general?
• do they offer meaningful coverage of statements?
• are they specific enough?
• do they cover possible edge cases?

[ancientTexts-net]

Reviewed all commit messages.
Reviewable status: 0 of 6 files reviewed, 5 unresolved discussions (waiting on @rady-ben)

[rady-ben]

combined

package.json, line 32 at r1 (raw file):

    "test:unit": "NODE_ENV=test jest ./src/core --coverage && cat ./coverage/lcov.info | coveralls",
    "test": "nyc --exclude-after-remap=false npm run test:e2e",
    "testJestEnzyme": "jest --watch -c ./jest.enzyme.config.js",

For now, there are two ways to invoke jest.

But if this PR is going to be approved, maybe we can refactor into a single (combined) script

I added the new script because I saw this error message when I run the existing script error Command failed with exit code 1. and the script stops and exits. and there in no watch, jest doesn't refreshes when I updated the tests that’s why I had the idea to add new command with the new tests.
an other reason for separating is that the existing test concern the differents APIs, however the news ones concern the react components

[rady-ben]

@ancientTexts-net
in this function I am testing the initial value to be true and the and when the user click on the button I test that that the setPreview is call with the false as param. which describe the switch from true to false.
but I don't know how to set realy the state on the component to false so I will be able to test the switch from false to true.
I found that in a class component we use something like this
wrapper.instance().setPreview(false)
I am looking for an equivalent for the hooks

[rady-ben]

@ancientTexts-net
how can I simulate the onEdit event with jest BlockEditable.simulate('onEdit', mock Event); doesn't work