It seems so 
from testing point of view (since I am backend QA) - i have test cases and I make test plan/scenario from it. I wouldn’t expect to maintain anything about the test plan/scenario since all my logic will be in the cases
In some large teams, the develop and QA teams are separate. The QA team expects to maintain more independent and stable test scenarios, so they need to fill in request values themselves in the test steps, rather than just accepting changes to the endpoint specs made by developer, which might lead to execution failures. This is the reason for our design.
I get the reasoning but that would mean that i would have to maintain the Endpoint Cases values but also the values inside the test scenarios steps for some of the same Endpoints
which doesn’t make much sense since i would have similar/same functional logic in 2 places
therefore it makes more sense to just keep my functional logic and scenarios in Endpoint Cases and then use import from endpoint cases and keep a reference not copy
the only use case that i see for the test step values modification is if i want to just check something temporarly so i edit it there, but if I find it as useful scenario I would definietelly add it to endpoint cases so it can be regression tested at any point etc.
overall I think some switch button for the values here would probably add more versatility to the app and different users might find it useful for them or not
But I wouldn’t bother you anymore, thanks for all the answers
I guess our main difference is that you expect Devs to maintain the Cases in APIs Endpoint specs, and that QA maintains the Test tab with scenarios
which is never the case in my company
Devs just build API and that’s it, all the cases(scenarios) are done by QA
In Apidog, the difference between endpoint cases and test steps is that the test step involves processes (such as loops, conditions, etc.). Of course, if you don’t need to use these features in your case, you can complete the test directly by use the endpoint case. Maybe adding a batch run feature to the endpoint cases could better meet your needs?
Well kinda yes
so the thing is this: I usually created endpoints with pre-post JS scripts where i would do my assertations, and I would just use Collection runned to run those requests
Actually, we have met some users with the same situation as yours, and we are considering how to optimize for you guys.
here I am kinda torn where I would do those things, on one side i have access to pre and post scripts in Cases
but then I would use test scenario just as “bulk runner for cases”
i just think my mindset is still left in Postman
and not grasped the Test Scenario use cases in apidog