This topic explains how to share projects and related test assets by checking them in and out of your existing source control system.
Key project artifacts are in ASCII. This makes it easy to maintain them via source control, and merge changes from multiple team members in a concurrent development environment.
To share projects and test assets using any source control system:
Other team members can access the project files by checking them out from source control.
Check in .parasoft [if present], xxx.vcproj files, and xxx.sln files. .parasoft will be in the same directory location as the .vcproj file for the project. It completely defines the settings of the existing Visual Studio project for C++test.
Do not check in temporary data/files (such as instrumented sources, compiled objects, linked test executables, and automatically-generated header files) with the project. By default, temporary files are in the.cpptest directory at the same level as .sln or .vcproj files.
- These files should not be stored in source control because C++test can automatically re-generate these as needed. Moreover, they might include non-shareable information (like absolute paths).
- If this data is currently being stored within your project, change the C++test temporary files settings as explained in the C++test User’s Guide.
A checked in/checked out project can be imported by opening the appropriate xxx.sln /xxx.vcproj file in Visual Studio. Changes to the project structure (e.g. adding new stub files, or new test case folders) are saved in the original user's xxx.vcproj files.