Replies: 1 comment
-
In the meantime, I have found a temporary workaround by doing this: // ...
data.ReprocessWithoutChanges();
string textV2 = data.ToString();
if (textV1 != textV2)
{
TestContext.WriteLine("Error with ReprocessWithoutChanges");
// The textV2 is supposed to be equivalent to the textV1, but is generated differently
await Verifier.Verify(textv2).UseParameters(name).DisableRequireUniquePrefix();
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I have a case with Verify that I'm not sure how to best handle. My unit test is:
The code looks like this:
I have to use
DisableRequireUniquePrefix()
because otherwise Verify is seeing that I'm trying to verify the same file. But in practice, that's what I would like.The problem with
DisableRequireUniquePrefix()
is that it doesn't differentiate the context between the 1st Verify and the 2nd, so I don't know which one is failing.Is there any way to differentiate in the error log these
Verify
steps on a same text?Beta Was this translation helpful? Give feedback.
All reactions