(I am just starting to play around with remote test execution and there isn't a lot of clear documentation, so I may simply be missing the basics.)
I have a VM configured as a Remote Execution Server and it is successfully running basic tests when initiated from within Test Studio and the Scheduling Server. In the last couple of weeks I have been redoing some tests to make them simpler and more flexible when handling errors, and in doing so I have copied some Coded Steps from other existing tests. This has ended up in a scenario where many of my tests will not run on the Remote Execution Server because they cannot find the elements I have added to the Element Library. To clarify, the elements exist in my library on other tests, but it seems that because they are not local to this specific test, the elements cannot be found. NOTE: The whole project runs great locally on Test Studio; it is only the remote run that fails to find the elements.
If I record on that test and click on the respective elements, creating steps that I don't need, then the test seems to run remotely without error. However, I will have to do this for hundreds of elements and it will be quite time-consuming. Is there a way to mass transfer project files / elements to the remote execution server so it knows what they are?
Similarly, I also noticed that when I duplicate a test to modify it and create a different scenario, it only brings over the elements that are created in Test Studio steps. Anything referenced in a coded step (i.e., Actions.SetText(Pages.WebsiteName.ElementName, text)) does not bring over the element, so if I later want to create a Test Studio step using this element, I have to re-record it in order to recognize it in the local test. Trying to select the item from "Elements" and use the "Step Builder" doesn't help, as it only shows the "Getting Started with the Step Builder" text when I go to Actions or Verifications. If I record that element once in the local test, then Actions and Verifications will display their options. Is there a way to bring elements into new tests without having to re-record them or manually copy Test Studio steps that include the elements?
(I hope I'm using the right terminology...)
Thanks ahead of time!