What is emailing email@example.com going to achieve?
You know what the use case is for the runner. It’s your product, you designed it.
If you are in doubt. Your product has some key elements that only work in the runner. The ones that are useful for automated testing, including setNextRequest and data driven tests.
This runs locally using the Postman desktop client, and until recently had no limits.
You’ve imposed a hard to understand limit, which makes the feature nearly unusable for everyone outside of an Enterprise plan. Even the professional plan limits look artificially low as its based on the team.
For pretty much everyone here, it would appear that you have done this solely to push the more expensive Enterprise plans. If you haven’t, then it would be nice to hear the rationale behind this move.
As mentioned previously, if a company is willing to pull or severely limit a feature that has been free for over a decade, then what other feature may you restrict in the future? (For example, pulling the support for Newman over the CLI, or perhaps sendRequest() next.
sendRequest uses no local resources, just like the Collection Runner, so I’m guessing its fair game.
The main issue here is a loss of trust.
I’ve only been using the product for six months, and was starting to get colleagues within my organisation to invest time to see if we should adopt more globally. We were using the free version and sticking the code in our code repository which was all we needed for our current requirements as we don’t design many API’s, we just consume others so I don’t need the documentation features.
There is always a risk in using free software, that it will be pulled or deprecated and that is always the risk you take.
However, now knowing that Postman appear to be in this camp. I cannot realistically continue to champion the product internally as I no longer know if key features may be removed or limited in the future.
This probably means we will now look for paid for software, but I doubt I would recommend Postman as an option because of what has happened here.
Enterprise is too expensive for our use case. Making you more expensive than SoapUI.
Adding new features to the top tier like your new CLI to streamline integration. That would be fine. But removing or severely limiting existing features is not a business practice that I can recommend.