I installed trial version of Test Studio in order to see if your is suitable for our needs. Normally we are not big fans of writing test script using only record and play functionality. We prefer to customize our test scripts code in Visual Studio so that's why I started to make some draft tests using Test Studio Express.
Until now I had some problems with some tests, after I exported them in VS I’ve seen that after each export a info appeared that informed that maximum number of the export was reduced. The problem is that right now I have only 5 tests which I can export to VS:( ... those maximum conversions are somehow blocking me to make all the tests that I need in order to cover my evaluation checklist points. Probably I will be forced to create another account after I will used even those 5 exports/conversion which I have available for the moment.
I’m a bit confused because I read on your site this trial version has fully functionality but it seems that the export to Visual Studio 2010 is limited to 15 conversions.
What I should do in this situation because those 5 conversions are not enough for me ?
Thanks in advance and have a nice afternoon
Best regards,
Mircea Sicoe
4 Answers, 1 is accepted
We'd love to hear some more details about your Proof of Concept plans and the number of tests you intend to create. As soon as we better understand your intentions we'll work on accommodating and supporting your needs during your trial. While it's true your trial is limited to 15 conversions, we do still consider trial mode to be fully functional. Each conversion you perform is accurate and usable, exactly the same as in the fully licensed mode. We limit the number of conversions specifically to prevent people from downloading the trial, recording 200+ tests, converting everything to code then abandoning Test Studio. In other words we don't want Test Studio trial mode to be used as a short cut for someone who intends to do nothing but coded functional tests and has no intention of purchasing Test Studio. On the other hand if a paying customer wants to use Test Studio for that we will fully support them.
I'd also be very interested to hear your reasons for "Normally we are not big fans of writing test script using only record and play functionality." Naturally we are big fans of the record and playback approach. We're a big believer in "the less code the better". But we're also not naive enough to fool ourselves into believing that's the only approach. Here are some of the advantages we think the record and playback approach has:
1) Quick and easy test creation
2) Easier test maintenance, less code generally translates to less test case maintenance
3) The definition for all elements used by all tests contained in your test project are stored and maintained in one central Element Repository. If you need to change how an element is found in your application, change it here in one place and it's automatically applied to all your tests. No need to update dozens of test just because a few elements got moved around.
4) Test Studio does support a mixed model where you can write just a few steps in code and leave most everything else non-coded. And, by the way, the trial has no limit on how many coded steps you can create, or how many tests you can create.
The vast majority of our customers are very happy with this approach. We're always very interested to listen to customer feedback and why they prefer the approach they have taken and I welcome your feedback.
Cody
the Telerik team
Test Studio Trainings
Rank 1
First of all I want to thank you for detailed mail. For the moment I'm not interested to make fully functional test scripts, I want only to record/test almost all the UI objects from our applications in order to see that they are recorded and converted correct (that's way I need multiple conversions). I already found a problem/bug (http://www.telerik.com/automated-testing-tools/community/forums/test-studio-express/general-discussions/573342.aspx ) which will be released in the next internal release. I don't want to buy a tool which doesn't cover our needs and to be honest it is not very cheap. After I finish this phase I want to test a bit performance and load parts because even those two are very important for us. As I said we decided to start the evaluation of your tool because we already using some controls from your company (first point) and the second point is that it supports a lot of technologies and the third point is that it contains performance and load testing.
Regarding writing vs recording test scripts topic, we prefer to have coded tests approach because:
1) we could integrate our test with our continues integration build and run them as "unit tests"
2) we can run those MS unit test (or other formats) very easy
2) it is more easy for our envelopment team to make review and maintain them (in case it is necessary)
3) sometimes it is more easy to customize your code when it is coded
4) (from my opinion) a good test engineer should have almost the same programming knowledge as a developer
I know that in the beginning it is more easy and quick to make test using record and play functionality but after you have structured a but your tests (i.e. each screen is a class, each action over a UI object is a method) it is very easy to create (and to maintain) tests, is like completing a puzzle.
Thanks in advance and have a nice day
Best regards,
Mircea Sicoe
I see the bug you are referring to. We're planning to release an internal build (NOTE: internal builds are considered Beta quality. They may have undiscovered bugs) containing this fix by the end of next week. We wouldn't want to sell you a tool that doesn't meet your needs either. It would just create frustration on both sides.
This may already be obvious to you, however just so there's no surprises, Test Studio Performance tests and Load tests cannot be performed using pure Visual Studio coded tests.
Just FYI, if you ever do decide you want to try it, we do support running Test Studio tests on a variety of continuous integration servers, including TFS and Microsoft Test Manager. In TFS they run exactly the same as unit tests.
I do have a couple additional questions for you:
1) If Test Studio would meet your needs, how many licenses are you considering purchasing?
2) How many conversions would you need during your proof of concept phase?
Cody
the Telerik team
Test Studio Trainings
I was just speaking with our team regarding the built-in trial limiter that is restricting you from converting more than 15 tests to code. Unfortunately, this is not something we have the flexibility of working around without a full license of Test Studio.
That said, you certainly have the ability to create (not convert) fully coded tests from scratch using our framework or use our 'Convert to Coded Step' feature (right click on any Test Step) which will convert individual steps to C# or VB.NET, while leaving the test in a TSTEST format.
Once you make your purchase, this limiter is lifted and you will be able to utilize this feature as often as you would like without any limitations.
We want your trial to continue and we are committed to work with you to clear up any remaining questions or doubt you might have regarding the product.
Thanks for your understanding in this matter - we'll be sure to reach out in a few days to see how things are progressing.
All the best,
Daniel Levy
the Telerik team
Test Studio Trainings