You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuation token fix for list tools in test plans (#1110)
- In the list tools of test plans: list_test_plans tool,
list_test_suites tool and list_test_cases tool; The underlying function
does not propogate the continuation token even when more test artifacts
need to be fetched.
- The default pagination for these tools is 200 and only if the
continuation token is propogated can the rest be fetched.
- The list_test_cases tool did not have continuation token implemented
in it previously, implemented that.
Changes:
1. Updated the list tools in test plans to use Test plans REST Api for
propagating continuation tokens correctly.
2. Added the optional parameter 'continuation token' to list_test_cases
tool.
3. Updated and Added unit tests corresponding to these tools.
## GitHub issue number
1069
## **Associated Risks**
- when the list of test plans or test cases that need to be fetched are
too large, there are too many mcp calls that need to be made since the
pagination size is 200 only.
- Also the response size of the rest API's are usually large and the
chat needs to make a seperate call to read the response from the file
where it is stored.
## ✅ **PR Checklist**
- [X] **I have read the [contribution
guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CONTRIBUTING.md)**
- [X] **I have read the [code of conduct
guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CODE_OF_CONDUCT.md)**
- [X] Title of the pull request is clear and informative.
- [X] 👌 Code hygiene
- [N/A] 🔭 Telemetry added, updated, or N/A
- [N/A] 📄 Documentation added, updated, or N/A
- [X] 🛡️ Automated tests added, or N/A
## 🧪 **How did you test it?**
Added unit tests to check for continuation token related scenarios.
Manually tested using prompts
---------
Co-authored-by: Krishna Prasath D <krid@microsoft.com>
Co-authored-by: Dan Hellem <dahellem@microsoft.com>
0 commit comments