microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
How to perform load testing in PolicyRecordingBot?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hi PolicyRecordingBot experts,
What is the best way when approaching load testing the bot? As far as I understand bot's design, it receives webhooks and data on 2 endpoints, HTTP and NET.TCP, from MS Teams bot.
From the test automation perspective, we have to buy MS Teams subscription for hundreds of users, create those users, make some Selenium coding that simulates users calling each other. Well, that sounds like an overkill, doesn't it?
Is there a way to workaround all of this and, for instance, send some media stream to the TCP endpoint and measure actual CPU utilization? What issues are arising with this approach if it's even achievable?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the PolicyRecordingBot design around its HTTP and NET.TCP endpoints first. Evaluate whether a synthetic media stream can exercise them without MS Teams subscriptions or Selenium, and identify how CPU utilization would be measured. Done should be a documented, repeatable load-testing approach with its limitations.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100