I've come across some issues when working on products and switching to/from the standalone version to the vs plugin. Problems such as renaming in standalone breaks the project in the VS plugin.
Is there any best practices when it comes to working with VS plugin AND the standalone? Are there any things that should be done to make a project able to move between vs and standalone seamlessly?
8 Answers, 1 is accepted
you need to be conscious of the changes you make. In the case of renaming a test - it will confuse Visual Studio. VS will think the renamed file has disappeared and it will throw an error to that end. You need to:
A) Remove the old file reference
B) Add the new file
Check out the following video:
There are other situations to look out for. Running a test that has coded steps in both Standalone and VS will cause the entire test project to be built. So you should be careful that all the entire test project is compilation errors-free at all times.
the Telerik team
Test Studio Trainings
this is becoming an issue for us as well.
We've noticed that if you have a folder structure like this
and you rename the top level folder (Top Folder), it doesn't automatically check out all the children from TFS and make the relevant edits in the tests
It's OK if you check out every single child file beforehand, but you need to know and it's not intuitive. Not only that, but if you check out a top level folder it doesn't check out anything that is in a folder that is collapsed, which can make the whole process somewhat tedious
We've also noticed if you delete a folder in Test Studio and then go to Visual Studio, you then need to manually edit the project file to remove the dangling reference since the project file and the file system are out of synch. I can see why this is happening, but it makes working in a mixed environment more complicated that it needs to be
I'd still like to point out that this is makes for a bad user experience.
Are you able to work in a mixed environment with any success? We are a few months into our project and we're finding that we're wasting a lot of time synchronising Test Studio and VS
We are creating record and play tests in Test Studio and scheduling tests and then we have some developers working in VS writing coded tests that are sometimes utilised by the record and play tests.
Have you got any tips for making this experience any more positive?
We ran into multiple issues working with both VS plugin and the standalone client on the same project. When it comes down to it, switching between tools has been challenging to the point where we individually picked a platform and stick with it. I personally use VS, my partner uses the stand alone client.
When I need to work on projects that he's been working on I re-export the project to VS do my work and commit it to subversion. We have found that going from VS back to the standalone client is fairly seamless, though we've had issues with project references not being transfered correctly in the past, though this doesn't happen often.
Our test plan is heavily influenced by data driven tests, and consequently I find myself writing a large portion of my tests in code. This is primarily the reason that I chose to work with VS because of the development environment is fantastic. The coding environment in test studio is sufficient for small stuff but definitely not for larger amounts of code.
tl;dr : yeah we have the same issues, we just picked a platform (vs or standalone) and went with it.
Thanks for the reply, that's very helpful and insightful and maybe provides a better way forward for us
Sounds like we're in a similar position where we really like the VS integration and the power and flexibility of writing coded solutions, but we need to get it to work with the record and play suite.
Reading between the lines, it sounds like you have multiple projects for different tests. We're trying to create everything in one (large) project with the intention that we can share tests and functionality. Is this something that you'd advise against?
Thanks for your help, it's great hearing from someone who is actually using the system. I read your testimonial today and it sounds like you are having success with the product which I'd like to replicate!
- We have 3 main products that we use test studio for. Each product gets it's own project.
The VS plugin offers recording, and I found it to be more responsive/better performance then the standalone client. In theory with the exception of a few select features everything that can be done in test studio can be done in the VS plugin.
In terms of test authoring, we try to break our tests in small pieces to be reuseable. Data driven testing where the data source is inherited can be extremely useful with scenarios that are the same (like logging in and out of a web site) but with different users.
Sharing tests between eachother has been essential to our success thus far. With the agile development methodology our developers are following, using the same tests in many tests makes updating them a breeze.
The testing framework provided by telerik is large, and takes a little while to learn, once you get past the learning curve creating reuseable data driven tests is very user friendly!
there's some discussion here on cross-edition testings (i.e. migrating your test project from VS to Standalone and vice versa). I've thrown together a blog post on the subject so if you have some time please take a look:
And let me know if you have any qeustions left unanswered here.
All the best,
the Telerik team
Test Studio Trainings