No option for Parameter values sync

Get Support
29

But I wouldn’t bother you anymore, thanks for all the answers :slightly_smiling_face:

30

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

31

which is never the case in my company :slightly_smiling_face:

32

Devs just build API and that’s it, all the cases(scenarios) are done by QA

33

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?

34

Well kinda yes

35

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

36

Actually, we have met some users with the same situation as yours, and we are considering how to optimize for you guys.:joy:

37

here I am kinda torn where I would do those things, on one side i have access to pre and post scripts in Cases

38

but then I would use test scenario just as “bulk runner for cases”

39

i just think my mindset is still left in Postman

40

and not grasped the Test Scenario use cases in apidog :slightly_smiling_face:

41

I think it’s just difference in behaviour between Postman and Apidog

42

and since my mindset is still “stuck” in postman mode it’s probably just needs some adjustments and time

43

since I have just found out about apidog last week so I am still testing it out if it can cover my use cases that i had with Postman :slightly_smiling_face:

44

So I guess my main confusion is where my logic should live, in APIs Cases or in Test Scenario steps

45

But I always found test plans/scenarios/execution runs to be kinda disposable things where you only check the reporting and execution runs

46

while the main logic is perserved toghether with API specification

47

for example it doesn’t make sense to me to have my pre and post JS scripts and assertions added to some scenario step where I would have to make sure it’s not deleted or the be reused etc. instead of just using it from Cases and maintaining it there.

48

But one can argue that like “APIs tab is for Devs and Test tab is for QA” so I would then just have smaller scenarios with JS scripts that would be re-used in a bigger scenarios and maintained only in 1 place but that kinda doesn’t go well in my brain organization :smile: