Test − Import test

1. In the Import Wizard, select [Test] > [Import Test] and click [Next].
   

2. Enter the information for the test to be imported and click [Finish].
   
   1. In [Import path], enter the path to import the test.
   2. In [Unit Test] group, check whether to import [Test] and [Test Data] respectively.
   3. In [Integration Test] group, check whether to import [Test].
      • When importing the integration test, it is imported with the test data in a set.
   4. In [Stub] group, select the stub to be imported among [Connected stubs] and [All stubs].
      • Connected stubs: It imports only the stubs associated with the test you want to import.
      • All Stub: It imports all the stubs in the path to import.
   5. In [Includes] group, select whether to import with fault injections.
   6. In [Option] group, select the method to import if stubs exist.

3. If there are items that the name has been changed or the file has been deleted when importing the test information, the notification windows is displayed, allowing you to select whether to import the information except for that items. This notification window is displayed only if the information was exported from Controller Tester 2.6.14 or later version at a time. If the information is exported from the other menu and previous version, the notification is not displayed.
   

4. If the same test exists in the project, select whether to overwrite the test. Select [Yes] to overwrite and select [No] to cancel the import.
   

5. After the import has completed, it is applied to the selected project.

Import information exported from Controller Tester 2.6.14 or earlier

1. Enter the path to import the test in [Import path].
   
   • If [testinfo.export] file exists in the test path to be imported, select the directory containing the file.
     If you import the information exported separately from Controller Tester 2.6.14 or less version, select the higher-level directory containing the information exported.
2. In [Unit Test] group, check whether to import [Test] and [Test data] respectively.
3. In [Integration Test] group, check whether to import [Test].
   • The test and data must always be in the same directory, and if it is not, the data is not imported.
4. In [Stub] group, select the stub to be imported among [Connected Stubs] and [All stubs].
   • For the stubs created in Controller Tester 2.3 version, or the stubs migrated to Controller Tester 2.6, if the same stubs exist in the project, the import cannot be carried out.
   • For the stubs created in Controller Tester 2.6 version, if the same stubs exist, you can select either not to import them optionally or to create as a new stub additionally.
   • There is no feature to link the stubs to the test in Controller Tester 2.3 version, so you need to link directly to the test when migrating to version Controller Tester 2.6 or later.
5. In [Option] group, select whether to overwrite the existing test files if they exist and how to handle them when the same stub exists.