Building and exporting test resources

This page applies to Apigee and Apigee hybrid.

View Apigee Edge documentation.

Note: Use local development with Apigee and Apigee hybrid 1.5 and higher.

Before you test APIs, you may need to build a set of test resources, such as API products, developers, or apps, that represent those same resources that might exist in the production environment in your Apigee organization.

Build and export test resources as described in the following sections. See also Managing folders and files in an Apigee workspace.

Before you begin: Familiarize yourself with the concepts described in the following topics:

• What is an API product?
• Registering app developers
• Controlling access to your APIs by registering apps
• Using key value maps

Building test resources

To build test resources, create a test bundle and edit the test resources defined in the following table.

Test resource	Description
API products (products.json)	Define the API products used to bundle APIs and make them available to developers.
Developers (developers.json)	Register the developers that will access your APIs.
Developer apps (developerapps.json)	Register apps to control access to your APIs.
Key value maps (maps.json)	Define the key value maps (KVMs) used by your APIs to store data for retrieval at runtime.

Creating a test bundle

To create a test bundle in Cloud Code:

1. Perform one of the following actions:

   • Position your cursor over the tests folder in the Apigee section and click .

   • Select View > Command Palette to open the Command palette and select Cloud Code: Create Apigee test bundle.

2. Enter a unique name for the test bundle and press Enter.

The test bundle is added to the tests folder in the Apigee section.

Configure the test resources, as described in the following sections.

Defining API products (products.json)

Define the API products used to bundle APIs and make them available to developers. For more information about API products, see What is an API product?

To define API products, update the products.json file using the configuration wizard (described below) or by editing the product.json configuration file directly. For a description of the fields in the products.json file, see Resource: ApiProduct.

To define API products using the configuration wizard:

1. Position your cursor over the products.json file for the test bundle and click . The Create API product wizard opens.

   

2. Step through the configuration wizard to auto-populate fields in the products.json file. The products.json file is opened in the editor.

3. Edit the configuration information, as required.

4. Select File > Save or ⌘S to save your edits.

The following example defines the myapiproduct API product that contains the helloworld API proxy.

[
  {
    "apiResources": [
      "/",
      "/*",
      "/**"
    ],
    "quota": "100",
    "quotaInterval": "1",
    "quotaTimeUnit": "minute",
    "name": "myapiproduct",
    "displayName": "My first API product",
    "proxies": [
      "helloworld"
    ]
  }
]

Registering developers (developers.json)

Register the developers that will access your APIs. For more information about developers, see Registering app developers.

To register developers, update the developers.json file using the configuration wizard (described below) or by editing the developers.json configuration file directly. For a description of the fields in the products.json file, see Resource: Developer.

To register developers using the configuration wizard:

1. Position your cursor over the developers.json file for the test bundle and click .
2. Step through the configuration wizard to autopopulate fields in the developers.json file. The developers.json file is opened in the editor.
3. Edit the configuration, as required.
4. Select File > Save or ⌘S to save your edits.

The following example defines the developer [e-mail]:

[
  {
    "email": "[e-mail]",
    "userName": "ahamilton",
    "firstName": "Alex",
    "lastName": "Hamilton"
  }
]

Registering developer apps (developerapps.json)

Register developer apps to control access to your APIs. For more information about registering developer apps, see Controlling access to your APIs by registering apps.

Note: It is recommended that you define API products and register developers before you register a developer app.

To register developers apps, update the developerapps.json file using the configuration wizard (described below) or by editing the developerapps.json configuration file directly. For a description of the fields in the developerapps.json file, see Resource: DeveloperApp.

To register developer apps using the configuration wizard:

1. Position your cursor over the developerapps.json file for the test bundle and click .

2. Step through the configuration wizard to auto-populate fields in the developerapps.json file. The developerapps.json file is opened in the editor.

3. Edit the configuration, as required.

4. Select File > Save or ⌘S to save your edits.

The following example registers the developer app myapp for [e-mail] and associates myproduct:

[
  {
    "attributes": [
      {
        "name": "sample_attribute_0",
        "value": "sample_attribute_value_0"
      }
    ],
    "developerEmail": "[e-mail]",
    "name": "myapp",
    "callbackUrl": "",
    "keyExpiresIn": "",
    "apiProducts": [
      "myproduct"
    ]
  }
]

Defining key value maps (maps.json)

Define the key value maps (KVMs) used by your APIs to store data for retrieval at runtime. For more information about KVMs, see Using key value maps.

To define key value maps, update the maps.json file using the configuration wizard (described below) or by editing the maps.json configuration file directly. For a description of the fields in the maps.json file, see KeyValueMap resource.

To register developer apps using the configuration wizard: 1. Position your cursor over the maps.json file for the test bundle and click . 2. Step through the configuration wizard to auto-populate fields in the maps.json file. The maps.json file is opened in the editor. 3. Edit the configuration, as required. 4. Select File > Save or ⌘S to save your edits.

The following example defines the mykvm encrypted KVM:

[
  {
    "name": "mykvm",
    "encrypted": true
  }
]

Exporting test resources to the Apigee Emulator

To export the test resources to the Apigee Emulator:

1. Position the cursor over the test bundle that you want to export and click .

   

2. If multiple containers for the Apigee Emulator are running, select the container to which you want to deploy the environment.

The active test resources appear in the Apigee Emulator, as shown in the following figure.

View the test resource contents to obtain specific resource information, such as an API key for testing which is generated automatically and included in the developer app test resource.

Next steps

Now it's time to deploy to an environment.