---
sourceDocument: Zurich Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-development

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Attachment test steps

# Attachment test steps {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Test an attachment-dependent business rule by uploading an attachment either from a form or from a server-side API call. For example, you can have a business rule that doesn't let you close an incident without an attachment such as a screenshot.

Upload from form
:   As a UI test step, the upload attachment step requires navigation to a form, which you
    can open using either Open a New Form or Open an Existing Record. Use Upload Attachments to select
    from the attachments that the test step adds to the form. When you select attachments to
    add to a form, the system waits to load the attachments before proceeding to the next test
    step. For more information on UI test dependency and wait mechanism, see [UI test steps](https://www.servicenow.com/docs/~Ycs2y9qzj8WoJU8uCtQGg "Test user interfaces by mimicking user actions and interacting with the visible components of a page.").

Upload from Server API
:   As a Server test step, the upload attachment step has no UI dependencies. Use
    Upload Attachments to select from the attachments that the test
    step adds to the record. When you select attachments to add to a form, the system waits
    for the attachments to be loaded before proceeding to the next test step. For more
    information, see [Server test steps](https://www.servicenow.com/docs/qeaavn7MIgM5o4MIfe3Ayg "Test business logic and background processes by performing operations on the server.").

## Design considerations {#attachment-test-steps__section_hhd_ybw_5hb}

Follow these design considerations for attachment test steps:

* All attachment steps require adding one or more attachments.
* The system rolls back any attachments by the step after the test completes.
* The system cannot roll back any existing attachments after the test completes.
* Avoid testing records with existing attachments to eliminate data dependency.
* If UI testing is involved, add the attachment to a form.
* When no UI is involved, add the attachment to the Server API.
{#attachment-test-steps__ul_a5w_bsy_qhb}