---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Test App Engine Management Center functionality on a non-production instance

# Test App Engine Management Center functionality on a non-production instance {#ariaid-title1}

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

Test App Engine Management Center (AEMC) on a non-production instance to confirm that everything is working as expected before moving to production.

## Before you begin

Role required: admin

## About this task

To test AEMC and pipelines before you proceed to a production environment, pick two non-production instances for testing purposes. Follow the Pipelines and Deployments guided setup as if one of those non-production instances is a production instance. Because the system doesn't verify that the instance type on the environment record is actually a
production instance, you can set the instance type to Production for the second non-production instance.

## Procedure

1. Begin the Pipelines and Deployments Guided setup tasks as detailed in [Pipelines and Deployments configuration tasks](https://servicenow-prod.fluidtopics.net/gJNQeEQR7akNKSuuPulu6A "As you work through the Pipelines and Deployments guided setup, you must perform different configuration tasks on each of your instances.").
2. When you begin the tasks to configure your pipeline environments, select one of your non-production instances and designate it as a production instance in the pipeline environment record.  
   For more information on the usual process, see [Configure your pipeline environments](https://servicenow-prod.fluidtopics.net/hJxuurdVY0ikEtekdvTA3Q "Set up your App Engine Studio (AES) production and non-production (for example, development, test, and/or staging) environments by adding the URLs and credentials used to access each instance.").
3. Test AEMC and your pipeline functionality.
4. When you're done testing, change the Instance type of the non-production pipeline environment record to the correct type of instance.