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 snapshots are stored in a separate files which is super-convenient for updating them, but makes reading the tests more difficult, because you don't have a test code and tests result near each other.
One could imagine a three argument form of assert_debug_snaphot_mathes, where the third argument is the text of the snapshot. It seems like this won't work, because updating the snapshot will require updating the source code, but perhaps it is possible? Snapshots have a well-defined header, so just grepping src for them should perhaps work? This sounds like a terrible idea, but I can see myself using it :)
The text was updated successfully, but these errors were encountered:
I made an attempt at this (before this library) to do this by using the file!-like macros and reading up the traceback but I found it difficult. I'd be up for making another go with some direction from someone who knows the language better
Currently snapshots are stored in a separate files which is super-convenient for updating them, but makes reading the tests more difficult, because you don't have a test code and tests result near each other.
One could imagine a three argument form of
assert_debug_snaphot_mathes
, where the third argument is the text of the snapshot. It seems like this won't work, because updating the snapshot will require updating the source code, but perhaps it is possible? Snapshots have a well-defined header, so just greppingsrc
for them should perhaps work? This sounds like a terrible idea, but I can see myself using it :)The text was updated successfully, but these errors were encountered: