Hello, now we choose a tool for Automated Testing, we want to buy your's solution and we downloaded trial Test Studio from site.
But we have some question.
First, our wpf application, uses also win32 OpenFileDialog, and if record the test, it's was handled by Test Studio, and test was not pass.
Second, the Test Studio work with RadGridView not always and most of all tests fails.
Third, if record long sequence actions of test, in most cases test will fail.
Fourth, how can we operate with preparing project files before running tests, can Test Studio copy, or delete some files before running test and how?
But we have some question.
First, our wpf application, uses also win32 OpenFileDialog, and if record the test, it's was handled by Test Studio, and test was not pass.
Second, the Test Studio work with RadGridView not always and most of all tests fails.
Third, if record long sequence actions of test, in most cases test will fail.
Fourth, how can we operate with preparing project files before running tests, can Test Studio copy, or delete some files before running test and how?
2 Answers, 1 is accepted
0
George
Top achievements
Rank 1
Rank 1
answered on 13 Aug 2014, 11:32 AM
Also we found troubles with recorder on Windows7 64 bit. If record test, then try to remove all steps, then try to record test again then recorder not started.
When try to execute recorded test it started app, then wait one minite and then starting to play test. it lengthens the process of writing tests
When try to execute recorded test it started app, then wait one minite and then starting to play test. it lengthens the process of writing tests
0
Hi George,
First, thank you for contacting us! I'd like to point you to some general guidelines in our support service which will help both you and us.
For unrelated problems like this, it is always recommended to submit them separately. You can actually submit support tickets from the account you activated the trial so that we investigate and respond for each issue and track all properly. This will also help our team to respond faster as well as let you submit some private data (unlike the forums).
On the OpenFileDialog, the fastest way to help there is get access to a sample application and test case running over that if possible. That way we can spot the problem and get back to you with our findings. Do you think you can send that for us to replicate locally?
The RadGridView problem - we will definitely need details here. How does the test fail? Do you get an error? You can use the Step Failure Details - Export option to share details with us so that we can assist further. This goes the same about your third reported (a test playback) issue.
For the case of preparing to execute tests, I can point you to the execution event handling for Test Studio tests. See the article here for details.
For the problem described in your follow up message - I assume there is some app process left idle due to broken communication with the recorder. If that is correct you can manually kill the process and try again. If you hit the "recorder not started" problem again, you can also check the Test Studio application log and send back to us any errors you spot traced there to confirm this is the case.
Again, it will be great if you submit each issue separately so that we can quickly respond and track each case accordingly.
Regards,
Konstantin Petkov
Telerik
First, thank you for contacting us! I'd like to point you to some general guidelines in our support service which will help both you and us.
For unrelated problems like this, it is always recommended to submit them separately. You can actually submit support tickets from the account you activated the trial so that we investigate and respond for each issue and track all properly. This will also help our team to respond faster as well as let you submit some private data (unlike the forums).
On the OpenFileDialog, the fastest way to help there is get access to a sample application and test case running over that if possible. That way we can spot the problem and get back to you with our findings. Do you think you can send that for us to replicate locally?
The RadGridView problem - we will definitely need details here. How does the test fail? Do you get an error? You can use the Step Failure Details - Export option to share details with us so that we can assist further. This goes the same about your third reported (a test playback) issue.
For the case of preparing to execute tests, I can point you to the execution event handling for Test Studio tests. See the article here for details.
For the problem described in your follow up message - I assume there is some app process left idle due to broken communication with the recorder. If that is correct you can manually kill the process and try again. If you hit the "recorder not started" problem again, you can also check the Test Studio application log and send back to us any errors you spot traced there to confirm this is the case.
Again, it will be great if you submit each issue separately so that we can quickly respond and track each case accordingly.
Regards,
Konstantin Petkov
Telerik