Hi, since I started using the Postman CLI, I’ve noticed that I’m required to use the Runner report, but it seems there is a limit on the number of messages I can print.
I often encounter errors that require printing long strings to capture the entire error information. Is there a way to increase or remove the limit so that I can print unlimited messages?
Hi, so I see no one is answering me I feel like I am working for Postman company to improve it.
To effectively handle test failures in Postman, I discovered a workaround that leverages collection variables to document the results. Instead of relying solely on traditional test assertions, which might have limitations in terms of error handling or output format, I store the outcome of each failed test as a string within a collection variable.
This approach allows for greater flexibility and avoids constraints on the length or complexity of the output. By using collection variables to capture detailed error information, I ensure that all test results are well-documented and accessible for further analysis, without being restricted by the built-in limitations of Postman’s test framework.
It’s frustrating that instead of focusing on improving the product, the Postman team seems more concerned with finding ways to charge users more for subscriptions. This is supposed to be a cutting-edge tool, yet it lacks basic features for debugging and documenting errors. The lack of meaningful support for these core functionalities shows poor judgment in product development priorities. Users shouldn’t have to come up with creative workarounds for fundamental issues that should have been addressed by the product team from the start. It’s time to start prioritizing the needs of your users over squeezing out more revenue.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
