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

--login option #27

Open
nolanlawson opened this issue Dec 28, 2021 · 4 comments
Open

--login option #27

nolanlawson opened this issue Dec 28, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@nolanlawson
Copy link
Owner

The --setup flag is good, but I wonder if something like --login username,password makes even more sense. Probably 99% of people just need to bypass a login screen and start testing their app.

Then again, there are security issues here (passwords in plain text), and maybe I'm better off teaching people how to fish rather than trying to give them a ready-made solution that may not work out-of-the-box (e.g. 2FA, or if there's an additional confirmation screen after the login screen).

@nolanlawson nolanlawson added the enhancement New feature or request label Dec 28, 2021
@andreasvirkus
Copy link

andreasvirkus commented Feb 9, 2022

How would --login username,password decide which fields to fill?

@nolanlawson
Copy link
Owner Author

I believe there are some conventions that password managers rely on, e.g. that the ID is always username / password or something like that.

@houfeng0923
Copy link

need a load a config file which explain local storage and local cookie and more

@unlikelyzero
Copy link

@nolanlawson just a FYI, this is mostly handled by the playwright project. I think I might give microsoft/playwright#14134 a try. Playwright managed a lot of this sort of thing.

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

No branches or pull requests

4 participants