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

Test should not pass if run_cmd hit time out while sending PIN/password. #14

Open
mahavrila opened this issue Aug 5, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@mahavrila
Copy link
Collaborator

I passwd argument is specified, run_cmd waits for "PIN for" or "Password" string. If it times out while waiting for pin/passwd the test should fail.

@mahavrila
Copy link
Collaborator Author

EDIT: this seems to cause fail in dev branch, while when kerberos-integration branch is used, it just pass.

@x00Pavel
Copy link
Member

x00Pavel commented Jun 1, 2022

run_cmd has to be replaced with a more general run function

@x00Pavel x00Pavel closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2022
@x00Pavel x00Pavel reopened this Jun 1, 2022
@x00Pavel x00Pavel added the enhancement New feature or request label Jun 1, 2022
@mahavrila
Copy link
Collaborator Author

run_cmd has to be replaced with a more general run function

general run command as implemented in V2 is wrapper for subprocess, while run_cmd is wrapper around pexpect specifically designed for testing logins. Tests relies on this functionality so I don't think it can be easily replaced by general run command.

@x00Pavel
Copy link
Member

x00Pavel commented Jun 1, 2022

run_cmd now has bad implementation, it wouldn't even do what the user (me) would expect from it. So, this function needs very strict revisioning if we would still want to use it because even with the old version of the library, we implemented in tests the fixture that does most of what run_cmd do, but from my perspective in a more clear way. So, ok, maybe simple replacing with the run command is not a very good idea, but run_cmd curtenly need an upgrade and can't stay as it it

@mahavrila
Copy link
Collaborator Author

I completely agree, run_cmd should be improved and maybe also renamed or moved to fixture. My only concern was to minimize rewriting of existing tests.

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

2 participants