Add global beforeEach/afterEach hooks

[brapifra]

In a nutshell

This PR adds 4 new global parameters: beforeEach, afterEach, asyncBeforeEachandasyncAfterEach that will be executed during the execution of any property.
It solves the issue #876

✔️ New feature
❌ Fix an issue
❌ Documentation improvement
❌ Other: please explain

(✔️: yes, ❌: no)

Potential impacts

None

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 131f119:

Sandbox	Source
Vanilla	Configuration
dubzzz/fast-check: example	Configuration

[coveralls]

Coverage increased (+0.09%) to 96.269% when pulling 131f119 on brapifra:brapifra/876/feature into baff08d on dubzzz:master.

[dubzzz]

Great job @brapifra!

I put some comments in order to ensure we preserve consistency across the primitives offered by the API.

[dubzzz]

Prefer using afterEach in that case:

Suggested change

	beforeEach(() => resetConfigureGlobal());
	afterEach(() => resetConfigureGlobal());

The global configuration specified by the last it will not be cleaned for other tests. Global configuration can spread across test files.

[dubzzz]

🤔 Actually we may even mock readConfigureGlobal and don't use any of configureGlobal or resetConfigureGlobal. But you can keep it that way for this PR

[brapifra]

Yeah, we could mock it. Although I usually prefer to write integration-like tests. But it's really a personal preference so I don't mind changing it 😄
Regarding the beforeEach/afterEach comment. I'm pretty sure jest runs each test module/file in isolation. Therefore, I think it doesn't really matter to use one or the other in this case...

[dubzzz]

Just to make sure, prefer a afterEach here

[dubzzz]

Same use afterEach instead

[dubzzz]

Suggested change

	beforeEach(() => resetConfigureGlobal());
	afterEach(() => resetConfigureGlobal());

I think it would be safer to always clean properly after the run. Cleaning before do not ensure we clean stuff for next tests.

[brapifra]

I've made most of the requested changes. Let me know what you think @dubzzz !
The only thing that I didn't implement was the error throwing when a synchronous property is run and there is some async hook set up globally. Maybe I'm missing something but... why would we want to do that?
IMO synchronous properties should simply ignore those async hooks instead of throwing an error. e.g.

configureGlobal({
     asyncBeforeEach: () => {
          console.log("I just want to run this with my async properties and I don't want to break the sync ones");
     }
})

[dubzzz]

Once again thanks a lot for this huge contribution. I added some comments and suggestions to update the code and offer more flexibility and sanity checks to the end-users

[dubzzz]

@brapifra Thank you so much for your work and time. Just a few remarks before we merge it. Really really thank for the time you already spent for this PR 👍 By the way, let's ignore the red codeclimate, I don't think that the error is relevant.

[dubzzz]

Perfect 👍

Great job! Thanks a lot for the Pull Request!
I'll try to release a new minor including this new feature very soon.