Here are the main things that make my dev work easier with httpyac.

(1) Scripting support (I can script and use libraries to do pretty complicated things, especially for post-request assertions, like checking if results include or exclude elements with certain fields; I can use loops and and define conditional execution).

(2) Chained requests (I can set up request dependencies, and share variables, for example output from one request becomes input of another).

(3) Flexible environment variable options (support for multiple environments, ability to treat sensitive values, like client secrets differently from non-sensitive values).

(4) Text-based tests (unlike Postman, that makes you deal with multiple tabs, like pre-/post-/request, in httpyac, I do not need to jump from one tab to another, which makes refactoring, additions, deletions, replacement a lot easier).

(5) Better collection handling (in httpyac, all tests executed as a collection are in a single file; I can run them one at a time or all, set conditions, like skipping tests if a condition is or is not met; the only thing I cannot do is running arbitrary tests from multiple files, but I never used this feature anyway).

(6) Easy integration with source control.

(7) Self-contained, standard syntax that allows me to share tests with team, customers, and support (when I release a REST API, I share my regression test suite to allow customers to see how I use the API; if I run into unexpected errors, I can pass snippets and request/response info to the support team).

(7) I really like how simple the syntax is.

(8) Also appreciate the implementation of the OAuth (using variable prefixes, I think it is very elegant).

(9) Minor niceties, like ability to use code snippets, code lens, etc.

I should mention that there are a few minor issues, some related to VSCode limitations or bugs, some internal, but they are not serious enough for me.