Skip to main content
Copy to Project copies one test’s name, goal, steps, expected result, and labels into another project. The original stays until you archive it. It drops the scenario, configs, and dependencies. For a test that uses those, recreating it in the destination project is less work than copying it and setting them up again. This is separate from exporting test cases. That export is a file for another tool or a backup. QA.tech does not import that file back as tests.

Copy one test

  1. Open Test Cases in the project that has the test.
  2. Open that test’s actions menu and choose Copy to Project. The action is available for one test. It is hidden when several tests are selected, so copy each test on its own.
  3. Choose the destination project and application, then Copy Test Case.
  4. Open the copy from the confirmation and check it.
The copy starts in the same Active or Draft state as the original. Archive the original only after the copy is in the destination project and you have checked it.

What the copy includes

The copy includes the name, goal, steps, expected result, and labels. It does not include:
  • Scenario. The copy is not filed in a folder.
  • Dependencies. Resume From and Wait For links stay on the original. Set them up again on the copy. See Dependencies.
  • Configs. Login and other configs belong to one project. Recreate the ones this test needs in the destination project and attach them to the copy. The copy dialog says the same thing.
Duplicate is a different action. It keeps the new test in the current project.

Chat assistant

The assistant in a project cannot create tests in another project, and a file it generates is not imported as tests. When the tests use configs or dependencies, open the destination project’s chat and recreate them there.