Releases: TestArmada/magellan
Make the stdout logging less verbose
This release reduces the stdout logging verbosity.
- added line-by-line filtering on certain conditions
- stop logging failed requests associated with /timeouts/async_script
Fix issue with successful steps not showing in log
PR: #292
The new logging filter i put in place in previous release was filtering out the individual successful steps.
updated the stdout white list to include the check mark so those steps get picked up
Cheers!
Fix issue with logging being too verbose
Users were having issues with the logging being too verbose.
This has been fix by making the whitelist be more "specific" ... plain "error" and "warn" strings were too generic.
the new white list should filter only what we need specifically targeting the color coded ERROR and WARN tags of nightwatch
Use strictly pipes in ChildProcess, also this fixes a bug with the reporters getting unfiltered stdout
Quite simple, use pipes in the ChildProcess.
This fixes a bug in where the reporters can be given the "unfiltered" nightwatch debug log, which is way to large for any reporter to deal with.
Cheers!
Make nightwatch err and warn visible in stdout
Currently the "ERROR" and "WARN" logs from nightwatch are suppressed when the debug flag is turned OFF..
and our users ALWAYS use the debug off, because if you turn it on your log will be filled with base64 screenshot gobbledegook...
Also, with approach taken, we will see all the "ERROR-ed" selenium request/response logs in the magellan stdout
Add error message context for when saucelabs capactiy limit is reached
this PR explains details of this release:
#285
A developer can be having their tests run in saucelabs,
and alot of the time these tests can fail because of lack of saucelabs capacity.
Currently, when a saucelabs capacity error happens, the error message produced says the following:
13:38:19 Error retrieving a new session from the selenium server
13:38:19 Connection refused! Is selenium server started?
this release just adds a little context to the existing error message, letting the user know the error may have been caused by a saucelabs capacity issue.
Cheers!
Catch unhandled errors
Merge pull request #282 from TestArmada/handle-uncaught-exception Do not abort on uncaught exception
PortUtil fix to check all ports
Fixed Magellan.portUtil.acquirePort to check all ports between BASE_PORT_SPACING.
For example. If the BASE_PORT_START is 12000 and BASE_PORT_SPACING is 3, it will check ports 12000, 12001, and 12002. If all are free, it will return 12000. If any of those ports are not available, it will then check 12003, 12004, and 12005 and so on.
Fix problem with "--help" option
Shifu botches up --help when loaded by init script. Fixed so the help loads before the plugins.
