I was just curious if instead of running elementor on the top of its own protractor session, you can reuse existing protractor and use your plugin to send commands to it.
Image a setup
a grunt / gulp enviroment that runs e2e tests, one of the tests is failing and a page that is visible after the user log in. So at that place you put browser.pause() to debug it.
Now I would run your elementor server that would connect to the existing protractor session and by using your chrome extension (i expect it would be already running with the protractor session launch from gulp/grunt) I would be able to find missing or problematic elements.
What do you think? I guess you have almost everything ready, it is just a matter of composition.
Hi Andres!
Thank so much for your great tool!
I was just curious if instead of running elementor on the top of its own protractor session, you can reuse existing protractor and use your plugin to send commands to it.
Image a setup
a grunt / gulp enviroment that runs e2e tests, one of the tests is failing and a page that is visible after the user log in. So at that place you put browser.pause() to debug it.
Now I would run your elementor server that would connect to the existing protractor session and by using your chrome extension (i expect it would be already running with the protractor session launch from gulp/grunt) I would be able to find missing or problematic elements.
What do you think? I guess you have almost everything ready, it is just a matter of composition.
I look forward to your reply!
Cheers, Andrej