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

Some option or step to not close web browser after running? - use -speed option #911

Closed
kensoh opened this issue Jan 9, 2021 · 4 comments
Labels

Comments

@kensoh
Copy link
Member

kensoh commented Jan 9, 2021

During recent training with an accounting SI, a question asked is can they leave the browser open after running?

And the current way is using -speed option (which supposedly is being deprecated).

What people want is not making it run faster, but having the option to leave browser open after automation.

This can be implemented on the option level (eg -keep_browser_open, or as a step within the flow eg keep browser open)

To chew whether this calls for adding something new to the tool. Am always careful to add stuffs. In theory there is no impact. But as time passes, more options and features and steps means users have to choose from a bigger list of stuffs to get to where they are going. This paradox of choice can often slow down progress. Especially when unnecessary.

@kensoh kensoh added the query label Jan 9, 2021
@macrocks
Copy link

@kensoh Not sure -s option is being deprecated but this option works perfectly and has helped me a lot in my automation as wel a few manual steps which are dynamic in nature.
I guess instead of adding more options for the same step doesn't make any sense until n unless it will not add any value.

@kensoh
Copy link
Member Author

kensoh commented Mar 3, 2021

Hi Amit, thanks for your feedback! If I ask you, we made TagUI default behaviour is always with speed option on, ie no restarting of browser for each row in datatable, and no added 3 seconds delay between each iteration. Is that good for you?

I'm considering for some users, they are running long processes taking 10 hours or more. If Chrome doesn't restart at all for so long, performance and automation problems might appear. So maybe add a new option to restart if this use scenario is common.

@kensoh kensoh changed the title Some option or step to not close web browser after running? - to chew Some option or step to not close web browser after running? - use -speed option May 21, 2021
@kensoh
Copy link
Member Author

kensoh commented May 21, 2021

Closing issue, since not closing browser is not a primary use case, users who want to keep browser open can use the -speed option. In future, if this becomes a major use scenario then we think of improving with another option with meaningful name.

@kensoh kensoh closed this as completed May 21, 2021
@kensoh
Copy link
Member Author

kensoh commented Jun 4, 2021

Hi @macrocks adding a new update at #1045 (comment)

Speed mode will be enabled by default for datatable batch automation, and browser will not restart after each run.

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