Verify multiple times within the same test method?

[glen-84]

I have code like this:

        await Verify(uploadDetails)
            .ScrubInlineGuids()
            .ScrubMember("Policy");

        var policy = Encoding.UTF8.GetString(
            Convert.FromBase64String((string)uploadDetails.Fields["Policy"]));

        await VerifyJson(policy)
            .UseFileName("test")
            .ScrubInlineGuids();

... but Verify only seems to work for the first call. Is this not possible?

I would have expected this to work, even without the UseFileName, by automatically appending an index to the file name.

I'm aware of #772, but even if it was possible (I'm trying to target a specific dictionary key), I think that it makes more sense for it to be written to a separate file, otherwise it looks like this property is actually an object in the first snapshot.

[SimonCropp]

try this

var policy = Encoding.UTF8.GetString(
    Convert.FromBase64String((string)uploadDetails.Fields["Policy"]));

await VerifyJson(new {uploadDetails,policy})
    .ScrubInlineGuids();

[glen-84]

It doesn't work with VerifyJson, only Verify.

Argument 1: cannot convert from '<anonymous type: Api.Modules.Common.Domain.Model.Files.UploadDetails uploadDetails, string policy>' to 'string?' [Api.UnitTests]

This still combines the result into one file, and the policy obviously isn't processed as JSON.

As mentioned, if they're combined then it's not really a WYSIWYG situation, the actual data doesn't have this separated policy property. That's why I'd prefer it to be written to a separate file.

{
  uploadDetails: {
    Url: https://.../test,
    Fields: {
      bucket: test,
      Policy: {Scrubbed} # Processed separately as JSON.
    }
  }
}

{
  expiration: DateTimeOffset_1,
  conditions: [...]
}

[SimonCropp]

can u share a failing unit test as a Pull Request

[glen-84]

For the error? I'm not sure if I'd want it like that anyway.

I see that you mentioned here that calling Verify multiple times is not supported. 😞

[SimonCropp]

you can call Verify multiple times, but you must supply some extra uniqueness. for example using .UseMethodName("customName")

[glen-84]

I had tried UseFileName. I tried UseMethodName now, and it still doesn't work.

[SimonCropp]

can you share your failing code as a pull request or in a new GH repo

[glen-84]

Apologies – I forgot that if the first verification failed, it would return early (due to the exception) and the second verification would not occur. It does in fact work.

Thanks for your help.

[zaus]

Just because I arrived here looking for something similar -- I ended up writing an extension method to tack on an "instance" of uniqueness:

public static SettingsTask UniqueForInstance(this SettingsTask verify,
      string instanceName,
      [CallerMemberName] string? callingMethod = null)
    => verify.UseMethodName($"{callingMethod}_{instanceName}");

Usage is then like:

await Verify(uploadDetails)
      .ScrubInlineGuids()
      .ScrubMember("Policy");
      // .UniqueForInstance("withoutPolicy"); // don't need this for the first one
      
      //....
      
await Verify(policy)
      .ScrubInlineGuids()
      .UniqueForInstance(nameof(policy)); // makes a second file with the instance suffix