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
I am working on a very big project and starting Wallaby for the first time and for an unknown location takes time (minutes). Starting (jest) tests in IDE also takes quite a bit of time so many developers tend to use jest-cli to run tests.
Tests with Wallaby takes less time, but this first "investment" is still something discouraging many developers from adopting Wallaby.
Question
Is it possible to generate wallaby cache for the main branch and distribute it to developer's machine so then can work with partially preheated data?
This would require a change in the diffing, as that would be not the diff created by the user, but the diff between the current branch and the origin.
Context
We have more than 100k tests and more than 1k developers, "reusing" at least something is crucial to unlock efficiency.
The text was updated successfully, but these errors were encountered:
Issue description or question
I am working on a very big project and starting Wallaby for the first time and for an unknown location takes time (minutes). Starting (jest) tests in IDE also takes quite a bit of time so many developers tend to use jest-cli to run tests.
Tests with Wallaby takes less time, but this first "investment" is still something discouraging many developers from adopting Wallaby.
Question
Is it possible to generate
wallaby cache
for the main branch and distribute it to developer's machine so then can work with partially preheated data?This would require a change in the diffing, as that would be not the diff created by the user, but the diff between the current branch and the origin.
Context
We have more than 100k tests and more than 1k developers, "reusing" at least something is crucial to unlock efficiency.
The text was updated successfully, but these errors were encountered: