-
Notifications
You must be signed in to change notification settings - Fork 29
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
Thinking of a new paradigm for recording #31
Comments
Sounds interesting. Juggling between the terminal and the browser is really distracting and annoying when I record something.
I'm not sure about this. I think that it is more flexible if I'm able to specify when a screenshot has to be taken. I end up editing the delays manually anyway. |
I've written down more thoughts locally. Option 2 is probably not doable realistically speaking. It's a cool idea though. |
Some delays are too short. It worked while recording, but they're too short for automated testing since we don't want false positives. And others are far too long because I needed to switch between the terminal and the window (and I needed some time to think about which button to press, maybe I need a new cpu 😄). |
Just to clarify: the short and long delays are all intentionally done by you using |
Yep, I'm always pressing the |
Just so that we're on the same page: live playback is |
Yes, I know. I'm working with |
Ah, alright. Yeah this is probably never gonna an exact timing because of selenium's own delays. |
Is selenium adding a delay between actions? If yes, is it just a rigid default value or determined by some event? |
I think it's just slow lol. It's faster for the chome driver. I chain up the calls without delay (unless there's an explicit |
It'd be really great if the user doesn't have to juggle between the terminal and the browser. The only way to do that is to have the screenshot taking action happen in the browser. Two options:
Both open doors to the possibility of removing the distinction between live replay and ordinary chained replay, since without the windows switching delay the whole testing can be replayed live without too much useless time gaps. Reducing the remaining time gaps can be done by Huxley itself when relevant, i.e. between keystrokes.
The text was updated successfully, but these errors were encountered: