[callsystem] CUTS Runner #93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
why am i supposed to review |
|
idk what hte fuck is going on :sad: |
artifishvr
reviewed
May 31, 2024
artifishvr
reviewed
May 31, 2024
artifishvr
reviewed
May 31, 2024
|
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 <[email protected]>
Co-authored-by: Arti <[email protected]>
Co-authored-by: Arti <[email protected]>
|
time for crack |
artifishvr
approved these changes
May 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.