BrowserLog | live log viewer with this tiny .net library

I am using protractor recently, and want to understand the best way of dealing with console.logs. For promise involved browser activity like click(),enter() which returns promise i am consoling in promise resolve in success block it works fine. But in other types of actions where i am required to use expect, expect itself resolves the promise returned by the condition and if i do try {} catch{} still that doesnt sound to be right way of console.log for that action. So what is happening is when i am doing console.log after expect action those gets logged prior to promise involved actions.

So how can i trigger the consoles which doesn't involve promise? Also as these gets logged prior to promise logs, does that mean the actions such as expect also occur prior to click() action?

Sample code for click() is as below //below the log happens after resolve.

Below is my code and I want to extract data under "specs" part like description, status etc. however I'm getting undefined when I capture the data and print it in the console. I have tried

The code works fine inside step definitions but not in after hook.

Below is my after hook code. It fails when I call attach function on world.

My overall goal is to extract the browser.manage().logs() to a helper function. I'm stepping towards this goal by including the browser.manage().logs() functionality inside the afterEach call inside the test.

I know that my test is throwing a console error.

The inline version of browser.manage().logs() will print the error. Neither the afterEach nor the checkConsole will print the logs.

What do I need to do to fix this?
Is the inline browser.manage().logs() retrieving the error and wiping the log? I've tried every combination of having them all commented out and the only one that ever works is the inline version.

I also have protractor-screenshoter-plugin configured and the report it produces shows the console error under the Show browsers logs button. Is this somehow grabbing the errors and preventing browser.manage().logs() from getting it?

conf.ts

I am running protractor tests on chrome headless in Ubuntu 16.04. The tests were running properly for more than 3 months but then suddenly the tests started failing with the below error-

npm run e2e console - Chrome not reachable error from the very beginning of the test

Chrome not reachable error after successfully running few tests

I'm trying to setup some simple protractor tests to try E2E tests with Angular2. I'm using the following versions : (v4.4.3 NG2 / v5.1.2 protractor).

I'm also using the latest @angular/cli version with the premade protractor.conf.js file.

Here is a simple test I've setup with my existing application.

I'm new of ruby and web development, i've searched a lot for this problem but i still not figured out.

I have a button :

I have a test which is navigating to a certain area of our application and then checking to see if there are any errors in the console when this area of the application is load.

The problem is that it is failing on a warning. Is there anyway from within my test that I can make it look just for errors and not warnings?