For me postman was a very important tool the last 2 years and even considering that iāll have to rebuild everything with another tool pains me greatly.
The paywall to an existing feature was very sudden and it hit us in a critical stage of development. Therefore i canāt help but see some resemblance to ransomware. Luckily iām used to Newman and I can make do with the Newman workaround for now. But what does the future hold?
I donāt want to rely on the whims of the creators of the tool that iām using. Abandoning postman will not be without difficulties, but if Postman decides to lock existing features on such a short notice with so little reasoning and transparency, the transition to another tool will become a necessity.
I have to reluctantly agree with Valentine - in my personal network I have never seen a Postman update land so badly. Reading a lot of blogs, comments and general posts about this. None are good.
Postman is a tool that I have a long relationship with and am a huge fan of. The community and positive regard for this amazing platform is unparalleled.
People feel very unsupported by this change, and Iām gutted for the team at Postman who have to support it. I hope all the bad press and feedback will encourage a rethink.
Iām following on a brilliant course about Postman and API testing by vdespa. I was experimenting with collection runs and from my experience 25 runs are not enough even for learning purpose.
I was evaluating Postman for API test automation in my company but I doubt that Enterprise plan will be within the budget. Basic/professional plans are more affordable for small companies but with these limitations they are not useful at all.
This is a sad moment for the Postman community. How is this pricing move aligned with Our Open Source API Philosophy | Postman Apart from the button in the UI how much of the local run is dependent on the underlying open source projects?
Work on load-testing features with cloud agents and make people pay monthly for actual cloud resources.
Well, Iām already pretty sure this limit was enforced after Postman 10.10.x.
So far, there is still no official explanation for users in this community.
I also donāt want to discuss the rationality of this disgusting limit.
Not only that, there is also no buffer time for free(even if basic&pro) users to accept this change, especially users who depend on Local Runner to debug test script.
If you guys want to avoid this limit, the urgent workaround is to downgrade to Postman 10.9.4(This shoud be latest version that is not affected by Runner limit, I have tested it).
So letās do this,
1. First, Backup/Export your Collections/APIs, if you sycned data to cloud, you can skip this step.
2. Block Postman auto upgrade by adding host 127.0.0.1 dl.pstmn.io in C:\Windows\system32\drivers\etc\hosts
3. Uninstall Postman v10.10.x and Install Postman v10.9.4, I have uploaded to Cloud Storage (to avoid Postman potentially maliciously deleting this old version)
4. Start Postman and import your data or login your account.
Postman has always believed in open dialogue with our community; we continuously make improvements and add new features based on feedback from our community of more than 25 million developers. We are transparent with our roadmaps, we constantly communicate our issues, and we support all major API specifications. Thatās the Postman open philosophy. But itās more than just a philosophy. We put our commitment to openness into practice every day. Below, youāll find details on a selection of these real-world efforts and projects.
I wonder which community feedback asked for the 25/250 monthly run limits.
To better align with the value Postmanās test automation offers for professional testers and quality engineers, we will make the following changes effective February 15, 2023, for free customers, and effective March 15, 2023, for new paid plan customers. Existing paid plan customers will see these limits effective upon plan renewal after March 15, 2023 (except Enterprise users, who have unlimited runs per month):
Local Collection Runner: Runs will be available with Free and Basic plans at 25 runs per month, Professional plan at 250 runs per month, and Enterprise plan at unlimited runs per month
Cloud-based Collection Runner: Runs will be billed on a consumption basis as part of the monitoring calls entitlement
Limits apply only to local runs via the Collection Runner, not via Newman or Postman CLI.
@alekdavis I think keeping these different public threads open, and the 1.5k+ feature requests from the community weāve implemented are a better testimony of our open source philosophy. That said if youād like to discuss the open philosophy feel free to open another thread as this is a bit off-topic here and Iād rather we keep the discussion focused on this specific change.
One of the key features which used to be free is now only really usable on the Enterprise plan.
So what you are saying is the value the test automation features offers is worth an extra 1200$ dollars per user, per year. That is the justification. You know that is more expensive that SoapUI?
250 runs on Professional considering its shared across the team will be used in no time at all for even smallish teams, so even Professional is of little use.
With SoapUI, there was always limits on some of the features. You need a paid for license to run the software in the CI, and for the reporting features, but it was always like that, so you knew where you stood.
The collection is akin to Test Suite, so you canāt even run a test suite in a tool designed for development and testing without having an Enterprise license.
I personally think you have shot yourself in the foot here. Youāve crippled the core product in what appears to be an attempt to push more Enterprise licenses.
I think you might find that you will lose out over time on all of the other tiers.
Users will try the free version first, hit the limit, and then go look at something else.
I would imagine that most of your Enterprise users try the free version first, and then for governance, require a fixed IP and the SSO consider Enterprise. I doubt anyone just jumps into an Enterprise license.
I would not think that limiting the collection runs is a feature implementation request coming from community users who are using postman free licenses or otherwise. I also would think that notifying the user community about this limitation well ahead of time would have been decent way to implement this rather than surprising them , so the vast number of tests that are implemented under collections are not runnable in a user-friendly manner (I know there is the newman way to run). jsut my 2 cents
Imposing a run limit on local collection runs in a workspace or sandbox may very well be the nail in the coffin for postman as a tool for my group. Anyone using postmanās collection runner to develop test flows for API testing will need to run collections over and over. It looks like postman is playing big brother here and setting limits on how many times I can āuse postman as a toolā to help me get my job done. I strongly believe this is the wrong path for postman. Imagine how many developers would continue using vscode if there were limits on how many times developers could run their programs! Postmanās collection runner is used in the very same way . Iām extremely disappointed to see this change of approach.
Postman is a great tool for beginners looking to get into automation.
The basics can be easily grasped by non technical team members too and it has a good helpful community.
The local collection runner is a very important feature and itās easy to go through 25 runs in a few minutes.
The enterprise licenses are extremely expensive for smaller organizations and teams to make a case for. Additionally ,with a change like this, we donāt know what else could be limited in the future.
I hope this decision could be overturned somehow or at least the limits scaled up to more reasonable numbers because it feels it will otherwise alienate a lot of users.
Iāve been using Postman for 3 years. Great tool. Iāve just joined a new company and got them to start using Postman last week. Then Iāve discovered this new collection run limit that is going to be imposed. This will make Postman virtually unusable for any test driven development unless you have the top tier license. As such, its no longer an option and Iāve been told to consider alternatives. Insomnia here I comeā¦
@cryosat-cosmologist@docking-module-part1 If possible, I think @norrispostman Code-First is the ultimate solution, If you donāt want to be locked in or forced to accept āgreat ideasā, after all something free is probably the most expensive thing, everything that is free will eventually become something commercial if they can, no one can always give selflessly all the time including open source project that I understand, just the rationality of commercializationā¦
This is such a shame. I was on the brink of adoption, but this limit and being in a small business just means we have to seek out alternatives now. I am already running 35 basic tests in the matter of 1 minute, so this limit makes the app sadly unusable. I hope Postman rethink this decision.
@swatchbookemma This limit is not on running individual tests but on running entire collections. If you run a collection that contains 35 tests it counts as 1 run.
In case you need to run these tests on a regular basis, have you looked at using Scheduled Collection Runs?
That said if youād like to discuss the open philosophy feel free to open another thread as this is a bit off-topic here and Iād rather we keep the discussion focused on this specific change.