It has caught us completely by surprise in the middle of a critical testing process. If this is not reversed we will move on to another tool (like SoapUI). We are not going to give second chances to find in the future that they limit later Newman or CLI if they dont get enough pay users.
Huh? I didn’t get the news until the paywall hit me. I’ll give them a month to revert this changes before i switch to an alternative.
Though I don’t want to start from scratch again, i don’t want to stick to a tool that feels like ransomware either…
And who knows what their next grand idea will be.
Making us pay to use the button in the UI versus running Newman in a shell is the worst product strategy move I have seen in a long time. Should we learn to use curl directly? It’s time to go test the competition The Collaborative API Development Platform - Insomnia
I’m a solo developer, using postman collection runs locally. I do probably 20-50 collection runs a day.
Looking at Postman’s pricing page, I’d now require an enterprise plan to continue running my collections (local, not even cloud).
@arlem Just want to post additional feedback like all the others.
We use collection runs in part of our Azure data factory pipeline tasks locally for building things out and testing them; also for local api testing in development. I would not say our team are “heavy” users of postman features, but it has been one of those reliable tools we’ve used in the background consistently. Our team has been paid users since 2017 at 10 seats. Even the pro 250 per month limit, It feels like a money grab. Feels like we were blindsided by this change.
I just want to share that this feature change has forced us to begin the business process of looking for a postman replacement.
Depending on the testing load, we can run over 100 in a day - and this doesn’t even count just running it locally. I shouldn’t need an account just to use the features already in the software that have been slowly stripped away, and we definitely shouldn’t need to pay to run postman collections. It’s hard to believe we’re now blacklisting postman from our company.
I guess the up side to all this is that we were forced to find a better solution with Bruno.
Been using Postman for many years, recently joined an Enterprise account with 200+ users. Been running collections manually for many years as well.
To find that Enterprise account is limited to 250 manual runs per month is absolutely shocking. I use it to debug E2E flows which are very fickle since Postman does not provide obvious automation tools to complement the run feature (like speed of each request, etc).
Great points by others - not using Postman resources other than the ability to share collections to others in the account, so why limit this?!? If every IDE monetized the debugging process, where would tech be now?!? I don’t know how much my employer is paying for this mega account with so many users, but it’s apparently too much already if Postman decides to cherry-pick features to nickel and dime their large customers.
I really had shied from SoapUI and warmed to Postman based on the UI, but Postman is apparently growing too big for britches. Yep, everyone is right - time to “MOVE ON, Beth.”
What a use case for switching to Open Source LOL. Note: commented using my personal account as to not identify my emp.
If my qa group already has collections that they run manually, will they have to change anything in them if I get the Enterprise plan? Do I stage a license file or do I have to create and use postman accounts and and store some stuff in the cloud?
I don’t know how you all do testing, but I expect to do many, many iterations - i.e., “collection runs”.
having to fork over $1,200 a year just to test my own local software?
Bruno is fine and is -actually- free.