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

Detect Ruuter functionalities that mix up responses #325

Open
4 tasks
Tracked by #256
turnerrainer opened this issue Jan 6, 2025 · 0 comments
Open
4 tasks
Tracked by #256

Detect Ruuter functionalities that mix up responses #325

turnerrainer opened this issue Jan 6, 2025 · 0 comments
Assignees
Labels

Comments

@turnerrainer
Copy link
Contributor

turnerrainer commented Jan 6, 2025

Note

This is a sub-issue of #256

AS AN Architect
I WANT to have a clear overview of Ruuter functionalities that mix up responses
SO THAT I could develop a better understanding of where the problem lies and how to fix it

Acceptance Criteria

  • Run at last 50 simultaneous requests per test
  • Report results before updates
  • Report results after updates / fixes

Scope

  • All Ruuter DSL-based functionalities, such as listed here (but not limited to)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Status: In Progress
Development

No branches or pull requests

2 participants