Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to stop closing chrome browser after flow execution #181

Closed
ramu-yarru opened this issue May 27, 2018 · 3 comments
Closed

How to stop closing chrome browser after flow execution #181

ramu-yarru opened this issue May 27, 2018 · 3 comments
Labels

Comments

@ramu-yarru
Copy link

Hi Ken,

Is there any way to stop closing the chrome browser after a flow execution (test)? Because the next flow being executed in my program is in continuation to the previous flow. If I can stop closing the browser, my thought is to check whether the next flow can be started from that point instead of opening a fresh browser and again start from begining, which will give faster response obviously. Here i can't combine the two flows due to limitations in my calling program. Could you please let me know is there any such feature available in TagUI?

Thanks,
Ramu

@kensoh
Copy link
Member

kensoh commented May 28, 2018

Hi Ramu, can you tell me more about the limitations why the 2 flows cannot be combined? There is tagui step to run sub-flows and also run step which can be used to run child-flows as a subprocess. You may want to try download the cutting edge version to overwrite your local packaged installation. And see if tagui step helps or the run step to run tagui command as a child-process helps.

At the moment, running TagUI with speed option will let batch automation run without restarting Chrome, but running separate flows will still restart Chrome. The reason is a technical limitation which requires starting a fresh Chrome session with websocket connection so that TagUI can talk to it, so the default behavior is killing after execution and starting again.

There is an open existing issue on Chrome but that one is to start in a separate process so that user's existing tabs don't get killed on running TagUI automation. I'll close the issue for now but please share more about your use scenario!

@kensoh kensoh closed this as completed May 28, 2018
@kensoh kensoh added the query label May 28, 2018
@ramu-yarru
Copy link
Author

My Plan is to invoke/call tagUI webservice flows from a Model based testing tool. As you aware, model based testing tool generate different test paths at runtime and one path may be continuation/dependent on previous path. So I want to retain the chrome session.

Thanks,
Ramu

@kensoh
Copy link
Member

kensoh commented May 30, 2018

I see, can you share what will happen if you combine the 2 scripts into 1 script? TagUI will be able to access other URLs halfway during execution to go to some other websites if needed.

Also, adding on, if visible Chrome mode is used, I think the session will remain as it is when the first flow is closed. If headless mode is used I think Chrome does not store the session details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants