-
Notifications
You must be signed in to change notification settings - Fork 1
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
[callsystem] CUTS Runner #93
Conversation
why am i supposed to review |
idk what hte fuck is going on :sad: |
i am SO sorry i have no idea how to suggest multiple lines other than doing that |
also bye butterroach :c |
dont request reviews from me i know nothing about the new code base |
its mildly humorous |
yoooo me neitherrr (also i will stop) |
its okay dw |
i worked on it and i dont understand half of what i did (i do but i have a stroke every time i read it) |
Co-authored-by: Arti <59352535+artifishvr@users.noreply.github.com>
Co-authored-by: Arti <59352535+artifishvr@users.noreply.github.com>
Co-authored-by: Arti <59352535+artifishvr@users.noreply.github.com>
time for crack |
Description
This PR adds a special callsystem for running CUTS tests. It simply adds an otherwise-dull runner with a special wake command (
cuts.run [CUTS unit test ID or "all" for running all CUTS tests at once]
). When this wake command is called, the CUTS runner will ensure that the test ID is valid and isn't a regular callsystem. If these conditions are met, the runner will pass context to the CUTS test to complete an activation. Results are piped back to the runner and are sent as necessary.Why is this useful?
As CUTS unit tests are expressed as otherwise-regular callsystems that use special methods in the CUTS SDK/API, running multiple tests simultaneously or running multiple tests in fast succession is incredibly unfriendly, i.e. one may run into rate-limits. Having a special test runner callsystem will help ease this common scenario.