Too long files when using parameterised tests #1646
-
|
I got an issue report from a user who is on Windows. Verify generates files with names like On Windows with NTFS it doesn't work because the file name is too long. I am wondering if there's a way to make file names shorter. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
here are the docs on naming https://github.com/VerifyTests/Verify/blob/main/docs/naming.md your file name is long because it is detecting the parameters from the ClassDataSource, and doing a tostring on those. basically it is treating it as parameterised https://github.com/VerifyTests/Verify/blob/main/docs/parameterised.md i think in your case you dont care about the parameter. so u can ignore it I would also argue since the test type name is here is a PR Eventuous/eventuous#472 eg this changes the path |
Beta Was this translation helpful? Give feedback.
here are the docs on naming https://github.com/VerifyTests/Verify/blob/main/docs/naming.md
your file name is long because it is detecting the parameters from the ClassDataSource, and doing a tostring on those. basically it is treating it as parameterised https://github.com/VerifyTests/Verify/blob/main/docs/parameterised.md
i think in your case you dont care about the parameter. so u can ignore it
I would also argue since the test type name is
AggregateCommandsTests, that a test method name ofMapAggregateContractToCommandExplicitlyWithoutRouteis overly verbose.MapContractExplicitlyWithoutRouteshould sufficehere is a PR Eventuous/eventuous#472
eg this changes the path