TestSprite is not required to build or use Qorx Community Edition.
For this public repo, the TestSprite check is a documentation and workflow QA check. It verifies that the repo points users to the Community Edition guide and does not expose a literal TestSprite secret.
For the hosted Qorx Cloud or Qorx Ayie onboarding site, keep a separate TestSprite suite against a public staging URL. That suite should cover Qorx Ayie Starter account activation, the 5,000 included Ayie/Cloud request counter, and the subscribe-to-continue state.
If a TestSprite key was pasted into chat, public logs, an issue, or a commit, revoke or rotate it in the TestSprite Web Portal before using it again.
Store a replacement only as a GitHub Actions secret:
TESTSPRITE_API_KEY
Do not put the key in .env, workflow YAML, docs, source files, release notes,
or screenshots.
The public workflow is:
TestSprite Enterprise QA
It is manually run with:
base_url: public staging URL for a product surface.blocking: true to fail the workflow when TestSprite reports a failing suite.Community Edition uses TestSprite for public docs and workflow QA. Local daemon, tray, account activation, and request-counter checks belong to the Qorx Ayie product flow suite.
Before relying on the cloud check, verify the repo wiring locally:
.\scripts\check-testsprite-enterprise.ps1
This check verifies the secret policy, public URL requirement, blocking mode, Community Edition guide, and the absence of literal TestSprite-style secrets.