newman feature request to turn off text wrapping or force a width larger than 60 for console.log events

feature request to turn off text wrapping or force a width larger than 60 for console.log events

Open cchretien opened this issue 7 years ago • 10 comments

The CLI reporter should have to ability to configure the text wrap limit for console.log events. In a build environment such as TeamCity we are restricted to just 60 chars. The requests api's and their stats are not wrapped at all. This behaviour was not present in release 2

The user should be able to....

to turn off wrap for console.log events
and/or, increase the default width from 60

Version and environment information:

Newman Version (can be found via newman -v): 3.5.2
OS details (type, version, and architecture): All Supported
Are you using Newman as a library, or via the CLI? Library
Did you encounter this recently, or has this bug always been there: encountered in release 3. Not present in release 2
Expected behaviour: ability to turn off wrap or increase text width that is defaulted to 60 for console.log events
Command / script used to run Newman: N/A
Sample collection, and auxilliary files (minus the sensitive details):
Screenshots (if applicable):

Steps to reproduce the problem:

engineer a collection, where in the test script, there is console.log instruction that prints out a string longer than 60 chars
run newman library in an environment where the shell is not a tty. (i.e. in a build environment such as TeamCity)
the wrap will default to 60

Note: I've tried setting TERM=xterm in the environment or CI=false

Sep 15 '17 15:09 cchretien

We could give terminal-width as an option for CLI reporter.

Sep 18 '17 11:09 shamasis

Hi,

Do you have any update here? I don't see a smart way to avoid the line breaks in jenkins. The current setup (line break every 60 characters), makes the output super ugly :-(

Regards, Timo

Feb 21 '19 22:02 timostark

Hi! Two Years of silence here. I find it still hard to read, when output is wrapped at col 60.

Can anyone take this task or tell me how I could contribute?

regards, S

Jun 25 '21 15:06 sstidl

Hello, any news on that ? The line wrap limit at 60 is reeaaaaal PITA , if you will :)

Jul 02 '21 14:07 ChieftainY2k

Yes, the line limit ruins logs quite badly and degrades their readability significantly. I wonder where would one start to tackle this issue? If someone could point in some direction, maybe we could collaborate together to come up with a fix. I can see that some start was made with https://github.com/postmanlabs/newman/pull/1230