Project Import/Export

You can import and export projects in the CLI environment.

Export command

You can export a project using the -e, --export <project top dir> <global top dir> <export dir> command.

• projectIE.exe path: Controller Tester installation path\plugins\com.codescroll.ut_ut_3.x.x\bin.
• project top dir: export target project directory.
• global top dir: tool global directory.
• export dir: Export output directory.
  

Export output

• io: Folder containing the interface implementation file used for target export. Appears on the global path and does not create it if it does not exist.
• target_server: Folder containing RTV target server information. Appears on the global path and does not create if it does not exist.
• factory: Folder used for class factory function. Appears in the project path and does not create if it does not exist.
• pa.ini, ut.ini: Project analysis and test configuration files.
• build.mk: RTV project compilation flag file.
• link.mk: RTV project link flag file.
• ctproject.json: Project setting information and exclusion information.
  • infromation: Project information.
  • exclusions: [Project] – [Properties] – [Inclusion and Exclusion] – [Excluded].
  • Inclusions: [Project] – [Properties] – [Inclusion and Exclusion] – [Included].
  • globalExclusions: [Window] – [Preferences] – [Exclusion].
  • utCoverageExclusions: [Project] – [Properties] – [Test] – [Exclusion of coverage].
  • utUserCodeInsertNodes: Fault Injection view.
  • utClassFactories: Class Factory view.
  • properties: Project setting information.
  • globalProperties: Controller Tester global setting information.
• ctsrc.json: Test target source file information.
  • name: Module name.
  • language: Target source language.
  • linkFlag: Link flag.
  • cmpileFlag: Compilation flag.
  • toolchainName: Toolchain name.
  • sourceTopDir: Source common parent path.
  • src.path: Source file path.
  • src.compileFlag: Compilation flag.
• ctaction.json: A file that defines actions to be executed for each step.
  • copy: Fields left by the existing copy action migration.
  • beforeCreateProject: Actions executed before project creation.
  • afterCreateProject: Action to be executed after project creation.
  • afterImport: Action to be executed after import is complete.
  • copy action: Description.
    • actionName: Action name.
    • from: Copy destination.
    • to: Path to be copied.
    • isDir: Whether a directory.
• ctmacro.json: The macro information inserted in each json file is replaced with the characters in the ctmacro.json file.
  • If you put it in the json file in the form of ${macro name}, it is replaced with the corresponding string when imported.
  • When exporting, the WORKSPACE and GLOBAL paths are created as blanks in the ctmacro.json file.
    • WORKSPACE: The workspace path of the project to be created when exporting.
    • GLOBAL: Global path of PC to be imported.

*The WORKSPACE path and GLOBAL path are required.

Import command

1. You can import the project using the # -i, --i <import resource dir> command.
   • import resource dir: Import destination directory.
2. Import will create a .import_product folder in the destination directory. In that folder, setup files (.cpi, .ini) and .bat files used for project creation and test export import are created.

*Create an exportTest folder in the import destination directory and copy the result of [Project] – [Export] – [Test] – [Export Test] to import the test when importing.