Hello,
I am evaluating this product for one of my clients. Although the record stuff seems to work nice, highlighting does not. On a high-dpi window (Surface Pro, Macbooks, etc), the highlighting is off. It should translate the coordinates based on the DPI settings of the system.
Can you please add support for any dpi?
Hi,
Our Quality Center config requires a Test ID value when creating a test case. Attempts to sync my Test Studio scripts to QC fails because a Test ID is not defined. Is the mapping to QC configurable? The script's UniqueID or a fixed value would suffice as the required Test ID.
Any suggestions for a workaround? I'd be surprised if I'm the first one to have this issue.
Thanks,
Dan
I have multiple tests that all pass successfully when run on Tests and Test Lists tabs within the test studio application, but when set to run at a specific time on the scheduler, they fail at some point in the middle of the test.
Conditions are otherwise the same (I have a windows process set up to make sure that they're even connected to the same router).
Here's an example log from one of the failed tests. These same failed steps pass when I run the test myself without the scheduler. I'm stumped. Anyone run into this or have suggestions on fixing it?
Lance
Overall Result: FailHi,
The issue I currently have is a little tricky to explain, so
feel free to ask for clarification :)
I’m running wpf. tests on an in-house application. Our
application uses integrated logins, so usually when I do standard workflows, I
let the app login automatically with my personal credentials. However, at times
I need to log in as a different user. In daily use we do this by holding
down F2 to break the integration and allow manual login.
Previously I could accomplish this during testing by a small coded step
with a keyboard.keyUp/Down event. However, this only worked because of an old
inherent error in the test application that would cause the initialisation of
the application to be halted until a dialogue was accepted, allowing us to
insert the keyboard event before full app boot up.
And now we get to the issue at hand: Since I updated to
current version of Test Studio and Runtime, that particular error message
caused TS to lose focus on start-up and the tests failed because of this. The
developers then fixed the error, so the message would not appear and the tests
would run alright. BUT, without the error message dialogue, the initialisation
of the application is not paused by anything, and the keypress event doesn’t
happen at the critical point. Thus, I never get the login box and am not able
to proceed with these particular tests.
So, based on this, can you think of a way to introduce the
F2 key event at the moment of initialisation? Or alternatively, is there a way to pass arguments to execute the application
so we can program a different start-up behaviour depending on the test?
Thank you,
Jakob
Hi,
Since starting to work with the Runtime licence, I've had a bit of strange issue. The first test list to run, whether it's a single test or a long list always fails. 0 steps will be run.
The second time I run (same test or any other), the remote test will initialise. This is a bit of an annoyance, to always have to run dummy test to 'wake up' the system.
Running from a desktop to a virtual machine with the runtime installed.
Any idea what might be causing it?
Error log example from failed run:
Compile failed: c:\Users\jw\AppData\Local\Temp\Projects\a0d7cce8-1f04-4e92-81c7-2877f8f4f7ce\OptemisRISTest\Automated Tests\Steps [ALL}\[NEWCASE] DoubleRead_Arvika_MRN_105.tstest.cs(86,61) : error CS1061: 'Optemis_RIS_Test.Applications.TMC_RIS_WorkstationexeApplication.Create_ExamWindow' does not contain a definition for 'TxtFamilyNameTextbox' and no extension method 'TxtFamilyNameTextbox' accepting a first argument of type 'Optemis_RIS_Test.Applications.TMC_RIS_WorkstationexeApplication.Create_ExamWindow' could be found (are you missing a using directive or an assembly reference?)
c:\Users\jweisbach\AppData\Local\Temp\Projects\a0d7cce8-1f04-4e92-81c7-2877f8f4f7ce\OptemisRISTest\Automated Tests\Steps [ALL}\[NEWCASE] NewPatientDetails.tstest.cs(80,61) : error CS1061: 'Optemis_RIS_Test.Applications.TMC_RIS_WorkstationexeApplication.Create_ExamWindow' does not contain a definition for 'TxtFamilyNameTextbox' and no extension method 'TxtFamilyNameTextbox' accepting a first argument of type 'Optemis_RIS_Test.Applications.TMC_RIS_WorkstationexeApplication.Create_ExamWindow' could be found (are you missing a using directive or an assembly reference?)
Thank you,
Jakob