msg.driver.session_.value_ not showing selenium session ID. theres many other driver/flow payload variables not showing

simonradier / node-red-contrib-selenium-wd2

Selenium nodes for Node-Red

Apache License 2.0

9 stars 7 forks source link

msg.driver.session_.value_ not showing selenium session ID. theres many other driver/flow payload variables not showing #4

Closed sudoritz closed 3 years ago

sudoritz commented 3 years ago

i dont know if this is causing anything else. but comparing original selenium-wd vs wd2 i noticed when viewing the payloadd i can see alot of flow/driver/sessionID info.

also when on wd/hub/ page wd2 doesnt let you take a screenshot in the flow or even delete session (it does but does give you error)

here is a view that shows it not passing VAR inthe payload (not sure if that is pushing issues to wdHUB

Here is the original version that you can see full msg object with session data tracking

simonradier commented 3 years ago

Ok, it took me time to found it. It is based on the new version of selenium-webdriver (4.0.0-x-Alpha). It does not rely on flow system anymore (this is why you can't found it). => It has a side effect where the session_ is not resolved as well (It was relying on flow as well and now relies on Promise) You can use the getSession function of the driver to query the sessionId.

sudoritz commented 3 years ago

so quick question so to get these Flow Variables back from Session Responses i would need to update my docker to selenium-webdriver 4.0.0-x-Alpha). ?