"TypeError: Cannot read property '0' of undefined" when test fail in jenkins
See original GitHub issue-
Newman Version (can be found via
newman -v
): newman -v 3.4.2 -
OS details (type, version, and architecture): CentOS 6.8 and newman_alpine33 docker image
-
Are you using Newman as a library, or via the CLI? CLI
-
Did you encounter this recently, or has this bug always been there: when
-
Expected behaviour:
-
Command / script used to run Newman:
-
Sample collection, and auxilliary files (minus the sensitive details):
-
Screenshots (if applicable):
when newman in jenkins and if fail test, newman gets error in cell.js
but sucessful in CLI
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (4 by maintainers)
Top Results From Across the Web
ERROR in Cannot read property '0' of undefined after upgrade ...
I have moved to a new (test) branch and isolated/deleted all new modules/components/files that have come from merge and after every change I ......
Read more >Cannot read property '0' of undefined" when test fail in jenkins
"TypeError: Cannot read property '0' of undefined" when test fail in jenkins.
Read more >Result screen not refreshing with error "Cannot read property ...
TypeError : Cannot read property 'toLowerCase' of null at ... Unhandled Rejection: TypeError: Cannot read property 'self' of undefined at ActivityService.
Read more >TypeError: Cannot read property 'debounce' of undefined
Unit tests failing: "TypeError: Cannot read property 'debounce' of undefined". Closed, ResolvedPublicPRODUCTION ERROR.
Read more >typeerror: cannot read properties of undefined (reading 'equal')
The function exported by the plugins file threw an error. We invoked the function exported by `C:\Jenkins\workspace\ABC\cypress\plugins\index.js`, but ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
What worked for me was not using
-t
in thedocker run
command. My exact syntax was:@kunagpal what was the solution to close this issue?