Add a test HTTP listener that can be started from UTs and responses can be tailored according to the test needs #74
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n be tailored according to the test needs
- Add UTs to test Invoke-OktaApiClient using the HttpListener when calling IWR
bryanapellanes-okta
approved these changes
Jan 15, 2025
Contributor
bryanapellanes-okta
left a comment
There was a problem hiding this comment.
A question of curiosity but approved 👍
| Remove-Module -Name Okta.PowerShell.PrivateFunctions -Verbose | ||
| } | ||
|
|
||
| It 'OktaApiClient should use the HttpListener when calling IWR' { |
Contributor
There was a problem hiding this comment.
Is IWR a known concept? What does it stand for?
Contributor
Author
There was a problem hiding this comment.
It refers to Invoke-WebRequest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Reproducing 429/retry issues is a complex task as we’ll need to interact with a test Okta org to force a 429. To facilitate the testing and resolution of 429 responses, we need to create a mock HTTP listener that can be started from UTs and where responses can be tailored according to the test needs.
What's changed?
Invoke-OktaApiClientfor testing purposesFix OKTA-849405