Project sharing scenario

When using the [Existing Projects into Workspace] function

1. When you create a RTV project, a RTV project directory (hereinafter referred to as RTV_A project) is created under the Controller Tester workspace.
2. The user who wants to share the project receives the RTV_A project directory created in the above step, and copies and pastes the RTV_A project directory into the Controller Tester workspace path that he uses.
3. Select top-level path to the project directory to import the projects using [Import] > [General] > [Existing Projects into Workspace] function.
   

4. Information required for the project is received from the RTV server, and [the toolchain or resource setting of the project is incorrect. If you want to reset automatically?], Click ‘Yes’ to complete the RTV setup (RTV server and toolchain registration used when creating the project).
5. You can see that an RTV project (hereinafter RTV_A’ project) with the same name as RTV_A has been created in the Controller Tester test navigator view.
6. Right-click the RTV_A’ project in [Test Navigator View] and perform [Reanalysis].
7. This should be done when connected to the same RTV server.

When using the [C/C++ Project from RTV Build] function

1. When you create an RTV project, an RTV project directory (hereinafter RTV_A project) is created under the Controller Tester workspace.
2. The user who wants to share the project connects to the same RTV server where the above project was created from Controller Tester that he uses, and registers the same RTV toolchain.
3. In the project creation wizard, select [C/C++ Project from RTV Build] to create an RTV project (hereinafter RTV_A’ project).
4. Import the $(project folder)/.csdata/link.mk file from the RTV_A project folder in the Controller Tester workspace and overwrite the link.mk file in the RTV_A’ project folder.
5. If you want to share the same test data, check the below.

*If the path where the source files are located is long, the entire source file may not be imported properly. If the path where the source files are located is too long, make sure to specify the CT’s global path just below the drive. (ex. C:\temp)
To modify the CT global path, open the CodeScroll.ini file in the location where the CT package is installed and replace the default under the -g option with the new global path to set.

*Even if you share the same project, coverage results may differ if you create each unit test. When you share a test, you must export the test using the [Export] > [Export Test] feature, and then import the test you exported using the [Import] > [Import Test] feature.