-
Notifications
You must be signed in to change notification settings - Fork 28
Open
Description
Background
We have previously performed REST API fuzz testing on the MPS and RPS cloud components using Microsoft RESTler, by running the services locally and fuzzing their Swagger-defined APIs.
Next Steps
As a follow-up, we want to revisit this approach and align as a team on how (or if) we should continue fuzz testing for MPS and RPS.
This work is intentionally exploratory and discussion-driven:
- Should RESTler-based fuzz testing be integrated into GitHub Actions, or
- Given that MPS and RPS are being replaced by Console over time, should this remain a manual, on-demand task where someone runs the fuzzer and captures results?
After alignment, the task includes running RESTler fuzz tests based on the agreed approach and documenting findings.
Acceptance Criteria
- Team agreement on fuzz testing approach for MPS and RPS (CI vs manual)
- Decision and rationale documented
- RESTler fuzz testing executed using the chosen approach
- Results captured and shared
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Todo
Status
Q2 2026