-
Notifications
You must be signed in to change notification settings - Fork 276
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 suite Feature/venom cli login tests #6783
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some general notes:
- We are not testing CLI login for Read and Write access, only Write access
- We are not testing CLI login against a real switch but using
radclient
on a default switch already created - There is no connection profile created to match on
CLI-Access
- We don't validate that a user in local DB can authenticate on the switch. Could be easy to do using a connection profile with an admin account and a local source
- Could you remove useless JSON payload when it's not necessary ?
t/venom/test_suites/cli-login-radius/teardown/00_clean_pf_config.yml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the moment, cli_login
test suite doesn't require other VM than pf
VM so it could be part of unit_tests
scenario to speed tests.
However, at some point, we may want to test CLI login with an AD source so in that case, we will have to boot ad
VM and certainly create a dedicated scenario.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another suggestion (for a next iteration): create a dedicated role to configure local RADIUS server on PacketFence to simplify reutilization
5fa3996
to
1c47ff0
Compare
4d7f533
to
066c23f
Compare
Pipeline to test: https://gitlab.com/inverse-inc/packetfence/-/pipelines/435898927 |
Hum, it fails but not on the configurator, not the test itself |
Add systemc ctl vor venom 1.0.0
Co-authored-by: Nicolas Quiniou-Briand <nquiniou@akamai.com>
add get_login_token in executor
add get_login_token in executor
Comment assertion (to be validated)
move to variables delete extra
1455dc2
to
b571482
Compare
I tested locally two scenarios and they work as expected. |
Description
Cover test for cli radius test
Impacts
Venom tests
Delete branch after merge
YES