For the complete documentation index, see llms.txt. This page is also available as Markdown.
New

Testing

Review automated test results for every app build version.

Testing shows you whether each build of an app passed its automated tests. Qore runs the tests on every build, keeps the result per version, and lets you open a full report. Open it from the app workspace's More menu → Testing.

The Testing screen, listing build versions with pass/fail results and case counts
Testing, listing test runs per build version.

The test runs

Each build version is listed newest-first with its result (passed or failed), a summary of how many cases ran (for example, 14 Passed · Total 14 Cases), and when it ran. The most recent build is marked Latest. Select View Report to open the full report for that version.

The test report

The report opens with the app name and the Version, the Commit it ran against, the Trigger (for example, OnBuild), when it was Generated, and the overall Result (for example, PASSED), followed by a summary of Total, Passed, Failed, Skipped, and Duration.

Below the summary, the results are broken out by suite — for example a frontend suite and a backend suite — each listing every test with its result, the file it lives in, the test name, and how long it took (for example, tests/App.test.tsx › renders without crashing, or app routes › GET /health returns 200 OK). Use Download to save the report.

A test report, with summary counts and results broken out by frontend and backend suite
A full test report.

Tests are tied to a build version and its commit and rerun on each build, so a report reflects a point-in-time version. Check the version before reading a result.

If a build fails its tests

A run's result can be failed as well as passed. When it is, open View Report to see which suites and tests failed and where, then fix the app in the App Workspace — describe the fix, or forward a failing test to the build agent — and rebuild. A new build produces a new version with its own test run.

Why this matters

  • Testing tells you whether a version is safe to publish before you deploy it.

  • Results are per build version, so you can confirm the exact version you're about to publish.

Security ScansApp Workspace

Last updated