Hi smoke maintainers,
We’re using mock sets to simulate different user roles. The documented filename suffix approach works as expected, e.g.:
get_parameter__set1.json
get_parameter__set2.json
According to the documentation, mock sets are selected via the __set-name suffix and smoke --set name.
What we tried:
For a clearer structure, we wanted to group mocks by “parameter” using folders and keep only the set name in the filename:
parameter/
get___set1.json
get___set2.json
get___set3.json
Note: we tried it with 2 and 3 underscores, both don't work
Expected behavior
Smoke resolves these the same way as the flat structure (i.e., folder name doesn’t interfere with set selection), or there’s a supported convention for “set folders”.
Actual behavior
This does not work properly (the mocks are not selected / resolved as expected when running with --set set1, etc.), only the default get_.json file is used.
Question
Is this intended behavior (mock sets only supported via filename suffix), or is this a bug / missing feature?
Thanks a lot!
Felix
Hi smoke maintainers,
We’re using mock sets to simulate different user roles. The documented filename suffix approach works as expected, e.g.:
get_parameter__set1.jsonget_parameter__set2.jsonAccording to the documentation, mock sets are selected via the
__set-namesuffix andsmoke --set name.What we tried:
For a clearer structure, we wanted to group mocks by “parameter” using folders and keep only the set name in the filename:
Expected behavior
Smoke resolves these the same way as the flat structure (i.e., folder name doesn’t interfere with set selection), or there’s a supported convention for “set folders”.
Actual behavior
This does not work properly (the mocks are not selected / resolved as expected when running with --set set1, etc.), only the default
get_.jsonfile is used.Question
Is this intended behavior (mock sets only supported via filename suffix), or is this a bug / missing feature?
Thanks a lot!
Felix