Ultimately this is a choice that we as users have to make. As mentioned before, for me this isn’t a deal breaker. If it is for you that’s entirely your choice.
I think your comment on the staff is a little uncalled for. The people responding in this thread did not make this decision, it’s not their fault, they simply work for the company and from what I have read so far they are trying to suggest alternative ways to complete your Postman tasks and providing information to try and help people understand what changes have been made.
Are they going to quit their jobs because they don’t agree with an imposed collection runner limit or push forward and do their best?.. I know what I would do.
I’m not trying to be obstructive here, I hear what you are saying… Like I mentioned before I’m an avid user of Postman and it is a shame that something that was free is no longer… but doesn’t that describe the whole world at the moment?
Netflix has increased prices (for the same service)
Amazon Prime subscribers will see prices rise from £79 a year to £95 a year (for the same service)
Twitter bought in a new paid-for service
BT recently increased my phone bill by £5+ per month (for the exact same service)
Slack recently implemented a change in subscription charges
EDF put my energy bills up (for the exact same usage)
Microsoft’s Office 365 price increased
To name but a few …
Granted the message could have been announced a lot better but why is it such a shock that a company like Postman also implements a new charge?
The thing I really don’t understand is the number of people saying that they now have to use workarounds and this is an issue? … Monitors, Newman / Cli, etc. aren’t workarounds, they are legitimate ways to run collections and it really doesn’t take much more effort or time to run in this way.
I also noticed on the same subject that people are saying setNextRequest is far more tricky to tweak and test using Newman … But you literally get the same output, which shows the order in which things execute:
And honestly, it took me about 30 seconds to export the collection and trigger the Newman run…
For repetitive tasks, I even created myself a batch file… so I can just click on the .bat, it prompts me for an output directory and a script file and then it auto-runs my scripts and produces a report. I use this when developing my test scripts etc. before pushing the collection to GitHub pipelines. I actually prefer doing it this way because I can be sure that the scripts will run exactly as they do in the pipeline.
As I said, this is ultimately a choice, for me, it’s not a deal breaker, I’ll be sitting tight for now.
I hope some of the suggestions I have made in this thread will help those that are looking for alternative ways to run their collections.