Available in: Project development through existing application checks and working previews. Isolated Project Tests depend on the prerequisites described below. Production verification on Sites requires its own authorized scope; this page does not describe a Chat or Agent test dashboard.
Testing checks that a specific revision does what you expect. Start with the user's workflow and the risks introduced by the change, then choose checks that can demonstrate the result.
Check a form in the preview
Ask the Project to add a required title to a sample request form. In the working preview, submit it empty and check that no record appears. Enter “Delivery note”, submit once, and check that exactly one record appears. For a separate working copy, open Tests and confirm the environment meets the prerequisites below.
Check the meaningful behavior
For a customer portal, useful checks might include signing in, reading an allowed record, being denied another customer's record, submitting a valid change, and recovering from a failed request.
| Check | Evidence |
|---|---|
| Access control | Allowed actions succeed and unauthorized actions fail |
| Application behavior | The expected result for representative inputs |
| Recovery | The workflow handles failure without duplicating effects |
| Runtime readiness | The intended revision starts and serves correctly |
| Security scan | Findings and coverage for the inspected source |
Use the Project's existing application checks and working preview where appropriate. Review Security findings alongside functional behavior.
Isolated Project Tests
Availability requires a configured Sandbox service, the required Test data structures, and a runtime reporting support for isolated execution, managed resources, cleanup, and usage. Interactive and API testing also require their respective runtime capabilities. Missing prerequisites make the corresponding workflow unavailable.
These availability checks are separate from end-to-end acceptance, which remains unverified for parts of the Test workflow. An available control does not establish that isolation, recovery, previews, or accounting have passed runtime verification.
A Test evaluates a separate development working copy and returns findings to the parent Project. It is not a production deployment or automatic code-promotion path. External service credentials can still authorize real external actions; isolated compute alone cannot make those actions harmless.
Record what passed
A useful result identifies the source revision, environment, checks performed, and observed outcome. State failed checks and unavailable coverage plainly. A completed operator response is not itself a passing test result.
Before releasing, check that the evidence applies to the revision being released and that database changes, background Jobs, and recovery have been considered. See Releases.
Example: report a complete check
For a request-board change, record the revision and environment, then report the checks you actually performed:
On this saved revision, valid requests persisted after refresh; missing titles were rejected; cross-user updates were denied. Email delivery was not checked.
Use actual observations in place of this illustrative wording. Link the result to the proposed release and identify any data migration or Job behavior that still needs verification. See Project release preparation.