Designing Platform Tests
Key Takeaways
Write the expected decision, data change, and evidence before running the test.
Use an authorized test tenant and sandbox targets for actions with side effects.
Verify expected allows and denials using the actual delegated user or integration context.
Document the difference between mocked workflow output, an executed action, and native target evidence.
Turn a requirement into a test
A platform test demonstrates a particular behavior in a named tenant using a defined identity, configuration, and input. Suppose operations wants a regional administrator to view a supported request queue and an automated process to send notice to a sandbox mailbox when a qualifying event occurs. These are separate assertions. Record which platform permissions the operator has, which data records should be visible, and which branch, recipient, and delivery result constitute success for the notice. A test using an organization administrator can establish basic availability. To verify delegation, repeat the relevant action with the actual privileges assigned to the delegated operator.
Use an isolated tenant and approved test data for a potentially writing operation. Confirm the tenant name, the API host and credential ownership where applicable, and the destinations of all outgoing effects. A test tenant can still be connected to live directories, mailboxes, or service endpoints if configured that way. Verify the connector target, email recipient, scheduled triggers, external web requests, and identity or account identifiers before executing. Use test accounts and harmless sample values where the workflow needs realistic input. Capture deliberate differences between the isolated environment and the eventual target, such as feature settings and object references.
| Test type | Example | Evidence to collect |
|---|---|---|
| Baseline | Read the expected scoped test object with the intended client or user | Tenant, identity or client context and actual resource returned |
| Allowed operation | View one request the delegated support operator should be able to open | Request ID, action and result under the operator's user level |
| Denied operation | Try to reassign that request as a read-only operator | Same request and actor, result of attempted action and unchanged owner |
| Branch boundary | Feed matching and nonmatching test events into a workflow | Step inputs, branches taken and expected outputs for both cases |
| External effect | Execute the notice into a designated test mailbox | Workflow result and receipt by the actual authorized destination |
| Post-deployment check | Verify that a moved configuration points to the intended live dependency | Selected draft, object-level outcome, and a narrowly scoped tenant test |
Separate preview from execution
SailPoint's workflow builder supports a test with provided trigger input and inspection of individual step inputs and outputs. Enabled actions in a workflow test really execute. Use a simulated step when you need to test downstream mapping without performing that step's write. In the test, turning the step off produces mock data. Review simulation choices step by step because other enabled actions can still execute. A simulated mail output can verify that a later step receives the expected data shape. To demonstrate delivery, run a controlled action against the sandbox mailbox and check the actual message. Include a nonmatching event and verify the workflow follows the intended stop path or omits the action. Record any test message identifier without collecting unrelated message content.
An imported configuration adds a different boundary. Configuration Hub backs up supported configuration objects. Set the source and target tenants deliberately and inspect the draft summary, where supported references can be resolved to objects in the target. A name match is useful only if the matched object is the intended dependency. Before deployment, confirm the operator and connector assignments referenced by the test. After deployment, inspect results per object, especially if the overall status reports a partial completion. Some dependencies require manual restoration, such as reconnecting a service desk integration to a virtual appliance. Check those references before interpreting an operational test. Configuration backup does not capture all tenant data or guarantee automatic reversal of native changes.
Define what qualifies as a pass
Write the test case with data, personas, steps, expected results, and actual results. For the requests example, a valid read by the delegated operator gives one positive result. Verify that the actor cannot reassign a request when using Access Request Read Only Admin. A good negative test uses a valid sample and the intended action. A missing sample or network failure exercises a different condition. On the workflow side, independently record which test activity was simulated and which action executed. Restore temporary roles, workflow configuration, and test data to an agreed baseline afterward. Save enough evidence to reproduce the observed effect after a configuration change.
See SailPoint's workflow builder and testing, user level permissions, Configuration Hub scope, and deployment drafts.
During a SailPoint workflow test, an action is configured with Enable Step off. Its mock data successfully feeds a later condition. What is established?
The simulated output exercises the later condition. Verify the actual action separately in a controlled sandbox.
Every action in the workflow was simulated automatically.
The first action really changed the target and the condition was bypassed.
The workflow is installed and enabled in the production tenant.
An access request support operator should be able to open a request and should be denied reassignment. Which test establishes the boundary?
Perform both actions as Org Admin.
Open the request as the support operator and infer reassignment permissions.
Use the actual operator to open a known test request and attempt reassignment, then verify the denial and unchanged owner.
Try to reassign a random request identifier using an expired API token.
Sections you finish are checked off in the contents.