-
Notifications
You must be signed in to change notification settings - Fork 71
chore: adds tests for oidc in vscode - VSCODE-414 #652
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
Conversation
Converting to draft since we might need to move the CI to evergreen. I will be looking into that. |
No need to move the CI to evergreen just yet. Fixed the issues that were there for our Github actions. |
src/test/suite/oidc.test.ts
Outdated
await testConnectionController.getActiveDataService()?.count('x.y', {}); | ||
|
||
// Minor pause | ||
await new Promise((resolve) => setTimeout(resolve, 500)); |
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.
Do we need to rely on this? Is there a different way that is not making the result subject to timing?
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.
Just addressed this in my recent commit.
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.
Couple smaller questions / thoughts. Nice tests!
Description
In this PR we have added tests for OIDC feature that covers all the applicable cases covered by compass as well as a few scenarios specific to vscode.
These are not E2E tests unfortunately, that is still an exploratory work in this PR
Checklist
Motivation and Context
Open Questions
Dependents
Types of changes