Alternative File-Based Source Control Systems

Test Studio can interact with any file-based source control system. Since Test Studio only integrates directly with Team Foundation Server, you will need to use a third party tool to check files in and out. Test Studio regards the projects as local, since files are not checked in and out within Test Studio.

 

Popular examples include:

• Git
• Subversion (SVN)
• Concurrent Versions System (CVS)

 

---

 

You will want to check in all files to your Source Control except the following:

• Pages.g.cs (or .vb) - this file is auto-generated with every build.
• *.suo files - this is a VS per user settings file.
• Anything in the TestResults folder.
• The project *.dll file in the project bin folder - this file is auto-generated with every build.
• If you also use the Standalone version, you will want to exclude the Results folder. This folder is only created by the Standalone version and holds the results of test list runs.

 

Here's a definition of some other files that test projects use:

• *.vsmdi - this is a Visual Studio file. It stores the definitions of Visual Studio test lists.
• *.testsettings - this is a Visual Studio file. It stores the test run configuration settings (default timeouts, default browser, etc.).
• Files in the Properties folder - this is created for every Visual Studio project. It contains definitions for the projects assembly.

 

These are the files that are unique to Test Studio projects:

• *.tstest (or .aii) - these contain the actual test definitions.
• *.cs / *.vb - these contain the code for your coded steps.
• *.resx - these contain the images for the Storyboard.
• Settings.aiis - this contains properties specific to this Test Studio project (e.g. tool version it was created under, Recording settings, assembly references, TFS connection settings).
• .aiilist - these contain the test list definitions.
• .tsprofconfig files in the Profiler Configurations folder - this is where the Performance configuration settings are stored. Whether or not to check in these files into Source Control depends on whether or not you want to save/share this information.