Skip to main content

Manage the Runtime Environment of APIs for Other Projects

Associating the Running Environment with Other Projects for the First Time​

When you select another project and import its data as test steps for the first time, to ensure that these steps can run properly and avoid unexpected issues with using services (Base URL), the product page will guide you to perform an "environment association" setup, which associates the environment of that other project with the environment of the current project.

Managing the Running Environment for Other Projects' APIs​

The association between the environments of other projects whose APIs are imported into the current project as test scenario steps, and the environment of the current project, can be viewed in the environment association function.

  • When importing APIs from other projects into test steps, click "Environment association" to manage it.

  • If the current test scenario has already imported APIs from other projects, a prompt will appear in the running environment of the functional testing, and you can click to manage it.

After entering the environment association function, you can see all imported other projects, as well as their environment association relationships with the current project and the specific services (Base URL).

Permission Control for Steps Imported from Other Projects​

Click the "Members" tab on the homepage to view or manage team members' permissions. If you do not have read or higher permissions for the target project, you cannot click to view or edit the APIs (test cases) imported from that project.

Viewing/Editing Step Details of APIs Imported from Other Projects​

To view or edit APIs imported from other projects into test steps, the operator needs to have "Read-Only" or higher editing permissions for the target project.

If you do not have the corresponding permissions, you cannot view or edit the API.

Running Test Scenarios Containing APIs from Other Projects​

To run test scenarios containing APIs from other projects, the operator needs to have "read or higher" editing permissions for all imported other projects. If you do not have access permissions for a particular project, you cannot run the test scenario.

Manually Synchronizing Environment Association Data from Other Projects​

To ensure data consistency, if the APIs or running environments in other projects have been updated, you can click "check the running methods of these steps" → "Update" button to update the cross-project data in the current test scenario.