We have multiple developers working on the UI tests simultaneously. We're using svn as our version control. I would like to know which files(e.g. Settings.aii, Pages.g.cs, .vsmdi) do we need to add to our svn?
Also, we implement the checking for FxCop and StyleCop for our codes. So when we try to convert our recorded steps into Nunit, the generated codes will hit the FxCop and StyleCop warnings. The workaround that we're currently using is to add
// <auto-generated />
tag at the beginning of our UnitTest.cs file to avoid FxCop and StyleCop checking for that file. Is there any other better or automated way to prevent this?9 Answers, 1 is accepted
You will want to check-in all files to SVN except the following:
- Pages.g.cs - this file is auto-generated with every build
- *.suo files - this is a VS per user settings file
- Anything in the TestResults folder
- If you also use QA edition, you will want to exclude the Results folder. This folder is only created by QA edition 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 WebUI Test Studio projects:
- *.aii - These contain the actual test definitions
- *.cs/*.vb - These contain your the code for your coded steps
- *.resx - These contain the images for the storyboard.
- Settings.aiis - This contains properties specific to this WebUI Test project (e.g. tool version it was created under, Recording settings, assembly references, TFS connection settings).
We don't have a better method for working with FxCop and StyleCop. Thanks for pointing this problem to us. I'll add a feature request to add better support for working with those tools.
Regards,Cody
Thanks for the fast response. I encountered another problem that all the aii files(including the aii test created on my machine and created by my colleagues). Attached is the screenshot of the error message when i try to open an aii file. Some of my colleagues have same problem with me while some don't have this problem. Is there any files that some of us forgot to check-in to svn? Can advice on this?
I am sorry the screenshot of the error was not attached. Can you please try again? Don't forget to click Attach Files after selecting the file to attach.
Kind regards,Cody
Thank you for the screenshot. We sometimes see this error the first time you open a WebAii test project right after performing an upgrade of WebUI Test Studio. The fix seems to be to close Visual Studio, restart Visual Studio and open the project again. Have you tried that? If you already have and you still run into this error message, please put your entire test project folder into a .zip file and attach it to post. We'll analyze it to discover what the problem is.
Kind regards,Cody
I tried to restart my VS and reopen my project but this seems doesn't help. I had attached my project here.
I loaded this project and did not have any problems with it. All tests contained in it load properly and it builds successfully too.
The steps I took to fix the "Operation could not be completed" yesterday when we tried to open that one WebAii test on your computer were:
- Exclude the test from the project (right click on it and select Exclude from project)
- Save and close the solution
- Close Visual Studio
- Restart Visual Studio
- Reopen the solution
- Add the test back to project (right click and select Include in project)
Once I did all of those steps the test loaded normally.
Cody
The *.tsprofconfig files are related to the Performance Testing. This is where the performance configuration settings are stored (such as the folder path where to store the test results, Performance server information, Performance counters, etc.) , so whether or not to check-in these files into SVN, depends on whether or not you want to save/share this performance test run configuration information.
All the best,
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.