Nicolas Dubien

@nicolas.dubien.me

661 Followers 886 Following

Author of @fast-check.dev (🌐 https://fast-check.dev) ∙ Lead Principal Software Engineer @GoPigment ∙ Opinions are my own #Testing #JavaScript #TypeScript #React

Diff being observed in my pnpm-lock.yaml file after I set the devEngines.packageManager to pnpm with a onFail set to download.
E-mail from GitHub telling me that I will not have LFS access for quite some time except if I take a data pack. My main repository is accountable for 4Mo of storage, what exploded is just the bandwidth, the rest is stable over time.
In case of random failure: 1. Failure will be reported 2. Failure will be simplified: smaller id, smaller date 3. Simplified failure could be replayed by rerunning the test with the seed and path provided in the error report
The main dormant bug in this snippet is that during a leap second Date.now() can go back in time by 1s. In this snippet we call it twice at two different points in time, as such the timestamp we get might be different...
Easily reproducible in case of failure, automatic shrinking capabilities to get the minimal error. All of that backed by fast-check
Tejas on stage
Photo of the main stage before the first talk at the opening
Just building one random number for each run
Multiple stickers with the logo of fast-check
Cup of coffee with React Day Berlin written on it
We launched @fast-check against our algorithm to get its help. It successfully detected an extra race condition and has been able to provide us with a very short reproduction plan for it. With that reproduction in mind we have been able to fix the last remaining race condition that we know of on this piece of code. @fast-check allowed us not only to find it but also to be more confident on our final fix.