This repository was archived by the owner on Feb 6, 2026. It is now read-only.
feat: add soak test execution to luminork#8255
Merged
johnrwatson merged 1 commit intomainfrom Jan 13, 2026
Merged
Conversation
Dependency Review✅ No vulnerabilities or OpenSSF Scorecard issues found.Scanned FilesNone |
johnrwatson
force-pushed
the
feat/soak-via-luminork
branch
from
4f96d67 to
985483c
Compare
stack72
approved these changes
Jan 12, 2026
Contributor
Author
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Adds the ability to execute a soak-type test via luminork-api-tests deno task.
You can now run something like this:
deno task soak:components -- --filter "Soak Test - Component Creation" -- --iterations 100 --threads 10Does it work? Yes I paged @nickgerace with it 🥇 https://systeminit.slack.com/archives/C06HZLN4BDM/p1768256358205769
All existing executions (in CI for Luminork validation tests or otherwise) use the deno reference for what tests to execute, so that should remain unchanged/correctly handled.
We'll use this as the first pass of our reporting framework for performance post-merge, I'll need to make further adjustments to make it output a proper JSON report so it can be processed/handled etc. But this gets us to a state where we can cleanly execution a simple soak test against an environment