Test run considerations for Postman tests

Before you can run Postman tests on IBM® Rational® Test Automation Server, you must read the considerations that you must take into account and complete the tasks indicated.

When you want to run Postman tests that you create in Postman, you must have completed the following tasks:

You must ensure that the Postman extension on IBM® Rational® Test Automation Server is enabled at the time of installation of the server software or is running before you add the repository that contains Postman collections to the server project. See Prerequisites for installing the server software on IBM Red Hat OpenShift or Prerequisites to install the server software on Ubuntu.
Restriction: If you add the repository with Postman collections to a server project before you enable the Postman microservice, the Postman collections might not be displayed in the Execution page for you.
You must have exported the following resources from Postman and saved the resources on your computer:
- Collections and their associated variables and environments from Postman in which all collections are exported as a single file.
  Note: You can export as many collections as you want.
  For more information, refer to Exporting a collection from Postman and Exporting data dumps.
- Environments configured in Postman, if you are exporting only the environments as separate JSON files.
  For more information, refer to Exporting environments from Postman.
You must have committed the following Postman assets or resources to the remote repository:
- Collections and their associated variables and environments that you exported. You can export all resources that are in your workspace in Postman. You can also export the collections along with the variables as a single file and the environments separately as another file.
  For example, you can save the exported file as MyCollectionsVarEnv.json that contains the collections, variables, and environments or you can export only the collections and variables as MyCollectionsVar.json.
- Environments that you exported, if you are exporting only the environments as separate JSON files. For example, you can save the exported file as MyEnv.json.
- An empty text file with the .postman extension that is contained in the same directory as the other Postman resources, so that the contents in the directory are attributed as Postman resources. For example, you can create MyProject.postman.
  Note: The .postman file enables IBM® Rational® Test Automation Server to identify the test resources as Postman resources.
  For example, if you have saved the Postman resources that you downloaded from Postman as follows:
  - MyCollectionsVarEnv.json or MyCollectionsVar.json that contains the Postman collections.
  - MyEnv.json that contains the environments associated with the Postman collection.
  The project directory can be as follows:
```
/Project
/Project/MyProject.postman
/Project/MyCollectionsVarEnv.json
```
  Alternatively, the directory can be as follows:
```
/Project
/Project/MyProject.postman
/Project/MyCollectionsVar.json
/Project/MyEnv.json
```

Restriction: You cannot run the test assets on a remote Docker host.