-
Notifications
You must be signed in to change notification settings - Fork 30
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: use kili_admin for tests that require org admin priviledges #1524
base: main
Are you sure you want to change the base?
Conversation
9392828
to
de6751a
Compare
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.
instead of moving all tests, we can create two kili client fixtures kili
and kili_admin
in tests/e2e/conftest.py
the kili_admin client use the kili_api_key_admin, and the normal kili client uses the kili_api_key
by default, all e2e tests use the kili
fixture (it's already the case)
and if some e2e tests require admin rights, we pass the kili_admin client fixture
b44204c
to
f18b5ef
Compare
do the e2e tests with exports fail when using the kili user client? (they should) |
there is no export e2e test |
notebooks the current solution only applies to python-modules e2e tests I wonder if we should do the same for notebooks too In the ci at the notebook steps, we should make the KILI_API_KEY with lower rights too |
e2e: https://github.com/kili-technology/kili-python-sdk/actions/runs/6420949015/job/17434205808