I have two steps that I want to run at the beginning of each test I've created in multiple projects. Is there a way that I can do that? I wanted to create the steps in one test and save them somewhere so when I'm building the next test, I can just pull the steps in. The only thing that will be different on each test is the URL that I'm navigating too.
Thanks,
Misty

Hi I would like to see what is the expression to use so the caption does not carry the version number.
Thanks!
I just updated to Test Studio 2016.1 version and I was not able to compile my projects.
I got the "Missing Assembily" Errors for all TestofArt classes.
After resetting the Assembilies in the setting tab, I was able to run the project.
But do I need to reset and re-import Assembilies for all of my exisiting projects after the update?
This may have been covered in an old thread but search turned up nothing.
Has anyone integrated TS with Mantis? I am helping a startup that just bought TS and has been using Mantis for a long time so they don't want to switch to another BT product.
Thanks,
-Eric
Suddenly I have encountered a compile failed error on remote execution. I got the following error under results:
Compile failed: c:\Users\Administrator\AppData\Local\Temp\2\Projects\172eb586-88ca-49d8-ba54-77c7a827f982\Trunk\Pages.g.cs(8826,39) : error CS1519: Invalid token '' in class, struct, or interface member declaration
Local execution is working OK. What could be the reason for such behaviour?

When building a verification step using Step Builder for a WPF test, the TextBox targets are incorrect for some TextBox elements, even though the Find Expression on each different TextBox is similar. As you can see in the attached images, the targets of the Verification Step in Step Builder are different even when both have XamlTag = TextBox as part of the Find Expression. These images also only show part of the issue, since sometimes no element-specific verification targets (e.g. TextBox, TextBlock) show up at all when selecting a TextBox element. We have tried a number of changes to see if we can alter the inconsistent behavior, such as relocating the element and altering the Find Expression afterward, restarting Test Studio, and manually changing XamlTag to see if the Verification Step targets change, however, the inconsistency persists. This makes it impossible to create a verification step to ensure the TextBox has the correct text value.
How can we work around this problem?

Greetings -
I've reviewed the help document "Merge Page Nodes" in order to merge elements in our WPF tests. After reproducing the behavior therein for Web tests, I'm at a loss as to how to apply this to WPF tests, since "Compare Mode" doesn't exist for WPF pages.
What I want to do is to merge all the elements which have the same Find Expression across all our WPF tests in the same project. How is this possible?
