My team and I are new to Test Studio. I'm sure this must be easy and we haven't worked it out yet...

We are a team of several testers working on the related projects and we want to contribute Web tests to a shared suite of tests in Test Studio, so that we can all access that suite of tests as it grows, and run those tests, edit those tests etc even if it wasn't us who created them. i.e. it's a team project rather than just a solo tester project. We may also add Manual tests, exploratory tests etc.

How do we do this please? We've got two users in different parts of the US who don;t know how to share tests but they definitely need to work on them together. I've looked at the TS documentation and I couldn't find any clues.

Many thanks,

Simon Rigler

 

 

 

Hello, 

TS Element Explorer is a useful feature to follow the page object pattern, however, it seems to be be oriented towards web pages in the web app. What if I have to write tests for a web app which has, e.g., navigation menu which is constant through the app pages?

Taken that I have the main page, the about page, the contacts page, etc. and on each of them a nav bar with items: MainPageLink, AboutPageLink, ContactsPageLink, etc. I can't see how to avoid mapping all the link for each page, instead once specifying an object for that menu with its links, and calling its instance on each of the pages under testing

Is it possible to ignore a step when a test is run in the context of a test LIST?

Hello-

My company has shut off access to the internet on the box in which I have Test Studio installed, all of my tests are against internal test environments and not "live" sites.  The issue that I'm running into is that the tool will try to phone home when I open a project, causing it to not respond and send an error that there was an issue when looking for an update.  It will also go into (not responding) when I'm running tests which will affect the results.  Is there a way to prevent the tool from trying to phone home?  I've looked through the configuration documentation and I can't seem to find anything.

Thanks, Jon

I basically have this in my test:

 

Logon

Do other stuff (with data)

 

How can i run Logon once, then run the "Do other stuff" step with each of the data rows?

Hello,
        I'm trying to figure out a way to click on the table row that has a variable name (that is it won't be the same each time I run the test). I want to be able to call the "click" method on the table row. Can you guys give me any tips in how to accomplish this? 

Using this following RadGridView 'Telerik.WebAii.Controls.Xaml.Wpf.RadGridView', what would be the most reliable way to set a filter on this GridView?

I've tried clicking the filter button on the column I would like to filter, but the XAML Path keeps changing, so it doesn't click the right column all the time...and I can't seem to find the proper way to do this in code.

 

Any help would be appreciated.

Hi,

We have an environment where the bamboo CI server is a remote server.  I cannot install test studio to it.  The instructions i found for integrating with bamboo show how to do it if all items reside on the same machine.  I wanted to be able to kick off test after builds on remote execution machines.  Any thoughts on this?

Hi Team,

Whenever I add tests to my list and run the same, browser closes for each test. Is there a way to keep it open and proceed with next test?

I have disabled close browser in property of last step, but it doesn't work. Please help.

WPF Application Dialog problem

So I have a bit of a strange problem with my test, so far handling Save As Dialogs have gone well, however this particular Save Dialog is not being 'detected' as a Save As Dialog. The title of the window is "Select an Export File" and my problem occurs when I click on the button to open this window, when it's opened I can see in the log file made by Test Studio that it is considered an "Unexpected Dialog". And then test studio won't handle it as a SaveAsDialog. However, when I set the UnexpectedDialogAction to Handle and Continue, what would be the Save As Dialog box is closed as fast as it is opened and if I open the Save As Dialog box again, then Telerik recognizes it as a Save As Dialog and not an UnexpectedDialog. Where this gets even more complex is when I take off Test Studio logging, the Dialog never changes to a Save As Dialog, and Test studio keeps recognizing it as an unexpected dialog no matter how many times I click on the button that opens this.

 

Any ideas on how I can fix this? Very confused about this issue.