Yes indeed I found your guide yesterday and I’d say thank you very much for this job that you did for the community
I haven’t found the part where you cover the topic related to multiple environments, like how can we decide to run on on dev or staging environment for example. On google people have different approches but it’s not very clear.
You can run everything in Postman for free? I run thousands of tests in postman for free in a few minutes - they also run every night & deploy.
Do you use newman to run tests or the postman UI (collection runner)?
I think Playwright is the current Hype + also from Microsoft, so I’m imagining if you use Azure DevOps, in the future there will be more out of the box support for it, maybe even standard integration. Huge community behind it, which is also important.
I personally still went with postman for this, just to have everything in 1 tool (for exploratory testing sessions). Postman supports all of the above, and basically any API testing tool, so no need to worry about these specs.
I’m not trying to push Postman here, but what do you feel comfy with AND your team?
Are there non-technical users? Does everyone want to use a Full-Programming framework?
Everyone always will have different opinions on how to do X or Y, you’ve just got to find YOUR way to do it, to see what’s best for YOUR organization. I would compare the things you’ve found, and tailor it to your specs & ease of use.
For now I only ran collections from the Postman UI, but yes probably I should consider Newman
In addition, I’d say 75% would not feel very comfortable with coding so Playwright could be a problem, but when I see examples on internet I saw that the code part is very low. I mean when you have some examples with assertions like “verify status, count, check a field in the response” then it’s almost always the same thing. Probably the setup it’s the hardest part.
Ah I see I need to write about that! (Multi environment support). The key with being able to run your tests against multiple environments will be your test data strategy. If you have hard coded ids in your tests and test environment but those ids don’t exist in the other environments you will face challenges.