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, as soon as withCassette finishes it dumps the accumulated cassettes to it's FilePath. This of course means that if several threads are recording to cassette which should be on the same path they'll overwrite each other. This is a common scenario as tests are often run in parallel.
Regardless of the solution, the thing should be more paranoid and error out if somebody have touched the file while it was running and it doesn't know hot to handle it.
If several recorders are writing to the same cassette those interactions should be merged together. This can be done either when
we save the cassette, by noticing that somebody have written to the file after we have started, reading that file and merging with it; or when
we add new recordings, by sharing the cassette for multiple threads if they are binded to the same path
The text was updated successfully, but these errors were encountered:
Currently, as soon as
withCassette
finishes it dumps the accumulated cassettes to it'sFilePath
. This of course means that if several threads are recording to cassette which should be on the same path they'll overwrite each other. This is a common scenario as tests are often run in parallel.The text was updated successfully, but these errors were encountered: