The model looks insufficiently restricted for API testing

[bogdanbranescu]

By offering a plugin as part of the base platform, please also consider a more keyword-based / YAML-structured alternative to what is currently offered. While clearly flexible, the code-heavy model can be a source of inconsistency (e.g. numerous equivalent ways to express the same thing, arbitrary function calls). I raise this issue because many aspects related to API testing are pretty standard (there are only so many types of entities attached to a request or expected from a response).

The coding capabilities need not be removed from this alternative, but certain aspects look repetitive enough and can be addressed case by case (for instance, checking multiple headers requires the same lengthy call many times). I understand that this means adding custom logic where out-of-the-box functionalities already took care of things, yet I consider this feature valuable as long as it does not eat too much development time.

What do you think is the proper way to include this functionality?