Skip to content
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

Added testresults client for TCM #555

Merged
merged 3 commits into from
Jun 20, 2023
Merged

Added testresults client for TCM #555

merged 3 commits into from
Jun 20, 2023

Conversation

triptijain2112
Copy link
Contributor

@triptijain2112 triptijain2112 commented Jun 15, 2023

Adding Test Results (TCM) REST APIs

@triptijain2112 triptijain2112 requested review from a team as code owners June 15, 2023 13:20
package.json Outdated Show resolved Hide resolved
Copy link
Contributor

@kirill-ivlev kirill-ivlev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@triptijain2112 triptijain2112 merged commit 55908ae into microsoft:master Jun 20, 2023
@mastrzyz
Copy link

@kirill-ivlev @triptijain2112 I'm a bit confused when am I supposed to use TestAPI vs TestResultsAPI

@triptijain2112
Copy link
Contributor Author

@mastrzyz For all your TCM or test related APIS (runs, results, attachments etc.), TestResultsAPI should be leveraged as they will be more performance efficient.

@mastrzyz
Copy link

mastrzyz commented Oct 5, 2023

@triptijain2112 that still will give our developers confusion, they are both the Same API's, before we ingest this change, can we have this clarified in the code?

maybe apply a deprecated classifier?

@mastrzyz
Copy link

@triptijain2112 ^^?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants