We are currently using a single project (VS2010) to manage all our test files (aii, tstest, their code-behind files and other associated cs and data files). However, as our test suite grows, that approach is fast reaching its limits (we are experiencing longer and longer times to load the solution, VS crashes every now and then, etc.). So we anticipate we are going to have to split up the solution into multiple smaller projects in the very near future.
However, I expect that the process to split the project is not as simple as creating the smaller projects and just moving files around. For one, I see that pages.g.cs (which contains all the element definitions) will need to be somehow "split" as well. Are there any other files that we need to consider?
Given this, please let us know if there are any proven (or at least recommended) ways to implement this. I have done some searching of this forum to see if this has been answered before - but couldn't find any posts in this regard. Please point me to any posts/documentation that I might have missed.
Thanks,
Shashi
3 Answers, 1 is accepted
I have some really good news I can pass along to you. We made this process fairly painless. You don't have to even think about Pages.g.cs. This file is dynamically generated based on all the elements contained in all your tests. See here for more details.
Since each test (the .tstest file specifically) actually maintains the definition for the elements it uses/acts on you can literally just move files around and the elements get carried along with it. A new Pages.g.cs will be automatically generated for your new project containing only the elements for the tests contained in that project.
The only "gotcha" you may have to deal with is tests that are used in our Test-as-step feature. Since we do not support using tests across multiple projects, you may have to duplicate your subtests in both projects. Except for this gotcha to watch out for, it literally is as simple as moving files around.
If you have any other questions, concerns or run into problems don't hesitate to reach out to us. We'll be glad to help you through this process.
Cody
the Telerik team
Test Studio Trainings
Rank 1
First of all, thanks for the lightning quick response (I wasn't expecting a response until at least Monday).
Thanks for the information - that is indeed good news. One follow-up question: Does this apply to the old aii files (created by TS's predecessor WebUI 2010) as well? Our project contains a mixture of both aii and tstest files since we have been using TS since the beginning of last year.
Thanks,
Shashi
Yep, this applies to the .aii files as well. There is no difference internally between .aii and .tstest files. Test Studio treats those two exactly the same. We simply started using the .tstest extension to be more generic but they are functionally identical to the .aii files.
All the best,Cody
the Telerik team
Test Studio Trainings