Using verify with custom verified file name

[lahma]

I'm investigating how Verify could be used testing esprima-dotnet. This means that we have bunch of JS files and their expected produced AST as JSON file. The common pattern among parsers / test suites is to have myfilename.js and corresponding myfilename.tree.json, but this is not set in stone (there might another naming too). But generally there are thousands of files available following this file-pair-naming for people wanting to implement parsers and verifying correct outcome.

Here's an example directory of JS input and expected AST JSON output.

Looking at these lines:

Verify/src/Verify/FilePair.cs

Lines 23 to 24 in 350bd3f

	ReceivedPath = $"{prefixReceived}.received.{extension}";
	VerifiedPath = $"{prefixVerified}.verified.{extension}";

It seems that the expected file name handling is quite set in stone. Are the any recommendations or ideas how to handle such custom workflow where input file -> parser -> in-memory-output is handled where one would like to use existing file naming without tightly coupling to Verify (basically allowing to use those expected files out in the wild, might be a git subtree too so cannot rename files).

I guess I'm asking for a feature to globally (or even per verify run) to provide a custom file name formatter, unless this can be achieved already otherwise?

[SimonCropp]

yes. currently the .verified. and .verified. are hard coded.

basically allowing to use those expected files out in the wild, might be a git subtree too so cannot rename files

I am not sure Verify provided much value in this case. Much of the value proposition is in the ability to automate the acceptance of changed files. In your case you never want to accept those changes. I suspect what you want is the diffing of file functionality. you can get this by using the lower level DiffEngine package https://github.com/VerifyTests/DiffEngine#launching-a-tool

[lahma]

Thanks for the valuable info. I'll be investigating the DiffEngine, thanks for pointing to it!