You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want test our fs components based on their properties instead of the specific scenarios we create for them right now. These scenarios are the edge cases we can think of and it is easy to miss other important cases. Property-based testing lets us lay bare the component and let automation poke at different points in its makeup.
There are two libraries to consider, proptest and quikcheck, but proptest is favored because it has a better "shrinker", even though it can be a tad tedious to write.
Coverage
Private filesystem
HAMT
Namefilter
Filesystem properties
Public filesystem
Memory Blockstore
The text was updated successfully, but these errors were encountered:
We want test our fs components based on their properties instead of the specific scenarios we create for them right now. These scenarios are the edge cases we can think of and it is easy to miss other important cases. Property-based testing lets us lay bare the component and let automation poke at different points in its makeup.
There are two libraries to consider,
proptest
andquikcheck
, butproptest
is favored because it has a better "shrinker", even though it can be a tad tedious to write.Coverage
The text was updated successfully, but these errors were encountered: