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
Currently vertigo expects that there are live test networks available.
Regularly one would estup several instances of ganache to allow for parallel mutation testing.
However, due to the nature of ganache this results in millions of files and hundreds of GB's being created over the course of one mutation run.
A more effective and user friendly approach is to dynamically create a new ganache instance for each test run, using a ramdisk rather than local storage.
This also removes the need to manually setup different ganache processes, which is another win in usability
The text was updated successfully, but these errors were encountered:
Just leaving a note in case this is not something you've already looked into. (And not sure this would really resolve anything)....
When the ganache server is launched within a JS script via the .server() method, it can be passed provider options. One of these is db which lets you specify an in-memory db store like memdown.
This seems like it would get around the files issue. I've also heard it's faster, although my attempt to benchmark did not really show much improvement so idk.
Description
Currently vertigo expects that there are live test networks available.
Regularly one would estup several instances of ganache to allow for parallel mutation testing.
However, due to the nature of ganache this results in millions of files and hundreds of GB's being created over the course of one mutation run.
A more effective and user friendly approach is to dynamically create a new ganache instance for each test run, using a ramdisk rather than local storage.
This also removes the need to manually setup different ganache processes, which is another win in usability
The text was updated successfully, but these errors were encountered: