New automated tests for Azure AI Projects SDK #41254
Merged
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
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
…12' into dargilco/projects-automated-tests-1
dargilco
changed the title
nick863
approved these changes
Jun 6, 2025
nick863
approved these changes
Jun 7, 2025
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.
Add automated tests for Python Projects SDK. Mostly newly written, inspired from existing samples.
Also update SDK to work around a service bug (Datasets DELETE operation should return 204, not 200 on success). I'll remove this once the service bug is fixed.
Looks like listing of Datasets is broken now, probably because the Foundry project we use for testing has a large number of Datasets. Up until now when we listed Dataset, there was a small number, and the results were all returned in one "page". Now we have a larger number, and the REST API to get the 2nd "page" using continuation token returns an error. This is probably because the service does not really support paging yet. I'll confirm with the service team.