Won't Fix
Last Updated: 28 Mar 2018 18:25 by Beth
Created on: 12 Feb 2013 21:32
Type: Feature Request
Access Test-as-Steps from different project
I have created a seperate project containing Telerik tests which I plan to import as 'TestAsStep' components into my main test cases.

However, I cannot seem to be able to locate then when i try to add them to the test.

The Visual Studio solution has the project where these components are located added to the workspace, but it's a different project then where the master test is located.

The reason why this is important to us, is because we have a number of different web-apps (verticals) that all share the some common basic behaviour (eg. Login to system, Search for User, etc). It is this common behaviour that we have modelled as individual web tests to be used as 'TestAsSteps' in all of our main projects for each vertical.
Posted on: 28 Mar 2018 18:25
I keep checking on this post to see if there has been an update.  We are having the same issue.  I think you have enough positive feedback by now to determine this is something that should be implemented.  Can we have an update ?  Even if there are NO plans to do this would help with our business decisions. 
Posted on: 09 Mar 2017 20:06
Day-by-day our project is getting larger and larger. There are few files which we are using in different project with same steps. In order to achieve this we are copying the files from existing project and maintaining same files in different projects which is not preferable, As i modify any one file and i am using it in three different projects. I had to update those files in other projects too which is an extra work involved.
Adding a test as step from other project is really a good and helpful feature which saves lot of memory and time.
Is there anything related to this implemented in recent times.
Posted on: 08 Mar 2017 14:28
I see the last comment on this was made almost a year and a half ago. Has there been any progress made on this?

Our projects are getting larger with ~4000 tests along with ~16000 element locators currently being loaded every time we open Test Studio. We’re finding the performance of the Test Studio tool is slowing down considerably due to the volume of test cases. 

We need to have the ability to separate our Test Studio project into different folders for each application we are testing, but we also want to maintain a common shared folder that can be accessed by each project. 
Posted on: 30 Sep 2015 13:06
Here is a feedback item that talks around this issue. So if you were unaware of this: in Test Studio, you can now see what Tests are being "Used By" other tests as step.  


Below is a related feedback item to this:
Posted on: 17 Sep 2015 21:53
Is there any update as to a line of sight on this functionality?
Daniel Levy
Posted on: 21 Apr 2014 19:12
If anyone subscribed is open to getting a sneak peak at what we are designing, in exchange for your feedback on if we've hit the mark - please send me a note: daniel.levy@telerik.com
Daniel Levy
Posted on: 21 Apr 2014 18:40
Thanks to all those who have up-voted. This is currently being reviewed and estimated for possible inclusion in a future release.
Posted on: 27 Feb 2014 21:43
I also agree. Test modules that are shared should be in a separate shared project. Other teams working on different projects can easily access the shared project. In addition, test steps in the shared project will also be up to date with changes. 
Posted on: 09 Apr 2013 05:25
Calling one script from multiple location (using Test as Step) has been very useful feature in our project. And we definitly want to continue with this.
Posted on: 28 Feb 2013 06:09
100% Agree. The functionality of "Add Existing Element" should give the user the option to copy the element into the project (as it does now) or to keep using the same file from a different location (i.e. different project folders).