Nicolas DUBIEN

I'm pretty OK for the idea of a custom reporter. Internally `fc.assert` somehow defines it's own custom reporter. The main challenge will be to investigate how we should adapt the...

No update for the moment, I'm waiting an update on the associated Mocha issue https://github.com/mochajs/mocha/issues/3992

@BourgoisMickael Sorry for the delay I just got an update on mochajs/mocha#3992. It seems that there is still part of the bug that's remaining. By the way, I am currently...

It seems that a fix might land soon in mocha. A Pull Request has recently been opened - https://github.com/mochajs/mocha/pull/4399 - to fix the ticket concerning doubled stack traces in mocha...

Depending when it will fully be supported by test runners, I'm investigating the idea to replace our composite error copying the original error into the final one by something native...

Would definitely be a good idea! I see at least 7 missing arbitraries or options: - one for unique symbols - one using `Symbol()`1 - one for named symbols -...

Thanks a lot for the report. There is indeed something to improve and do here ;) Indeed as said in https://github.com/wallabyjs/public/issues/2459#issuecomment-650854293, fast-check totally wipes the original instance of error that...

@dbartholomae Now that v3 is coming very very soon, I'm checking this issue to make the breaking change in the API for v3 and not wait yet another release for...

Step 1 and 2 of my plan described on https://github.com/dubzzz/fast-check/issues/660#issuecomment-651362595 have been released in v3. For the step 3, I'm thinking about many things to get proper errors: - Copy...

Add new Object.* calls done for record to the list of stable ones and test all of them against poisoning to make sure they will never break too much in...