Closed beam-me-up closed 9 months ago
Hi @beam-me-up. I'll check a bit various scenarios and get back.
This commit https://github.com/Endava/cats/commit/662412837b4d2724ab6ec7e1ad823a4169f74bad along with the fix for #75 will allow setting null values the way you have it in your example file. It will be available in next release.
This is available now in: https://github.com/Endava/cats/releases/tag/cats-9.0.2
@beam-me-up can this be closed now?
Yes please. Thank you.
In my CATs test scenarios, I've noticed a behavior related to setting values as "null." While I can use the "cats_remove_field" flag to remove parameters for GET requests, I'm facing a situation with POST requests where I want to set a parameter's value as NULL without removing it entirely.
Examples:
For instance, consider the following YAML examples:
In this case, I can use "cats_remove_field" for GET requests to remove the "status" parameter completely.
However, for POST requests like this:
I don't want to remove the "name" parameter, but I need to set its value as NULL.
Question:
Is there a way to set the value of a parameter as NULL explicitly for POST requests in CATs, without removing the parameter itself?
Any guidance or solution for this situation would be greatly appreciated.