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
Consider using cache versioning prefix for breaking changes
With certain versions the cache may break, so this would allow to migrate easily, multiple versions can coexist, easy rollback, no manual cache cleanup needed between versions
Why
With caching, it's difficult to tell which screenshots are associated with a given test. The screenshots should be somehow associated with the cached test.
All cached tests are stored in a single file cache.json. With a project that has many tests, I think that could cause problems. Also, is hard to find and debug a given test.
Example
No response
The text was updated successfully, but these errors were encountered:
What
<TIMESTAMP>—<SHA-1>.json
Why
With caching, it's difficult to tell which screenshots are associated with a given test. The screenshots should be somehow associated with the cached test.
All cached tests are stored in a single file
cache.json
. With a project that has many tests, I think that could cause problems. Also, is hard to find and debug a given test.Example
No response
The text was updated successfully, but these errors were encountered: