There are certain scenarios where the functionality represented by "finally" in the "try... catch..." scenario is needed. A function or step which can be executed at any point when the failure of the step occurs is welcome.
we are using hp alm for our requirement/test management tool and would be nice to have some integration to get the test results from mobile app testing reflected in that Matrixed environment
If you delete files or folders from your test suite using the TS standalone IDE, the Visual Studio plug-in will not detect the deleted files/folders when you compile your project so you must re-delete them there too.
Test Studio Results could be synced to HP Quality Center only once. Each action after that does not change their state - their status (Passed/Failed) cannot be seen, test results under a test set cannot be seen and synced. Adjust Test Studio results to be compatible to be synced in HP QC.
It would be very nice if the trial version had some more links to information and youtube video's f.i. if hovering on some items. f.e. how can i use the local data in a test step?
A project's BaseURL appends a slash after the URL is entered into a Project's settings. This is not idea in environments where you URL's are parsed like the following: 1) Protocol: http:// 2) Environment: dev, uat or blank 3) Sub Domain: admin, shopping 4) Domain: mycompany.com So when the base URL for the dev test list is "http://dev" for example. It navigates to http://dev/shopping.mycompany.com. It would be preferable in some cases if the test would navigate to http://devshopping.mycompany.com. To achieve that, there needs to be a method to remove the appending slash from the Base URL.
The test list events are fired in case of running on the scheduling server, however the problem occurs in case of running on the execution client setup (out of the server). Steps to reproduce: 1. Create your own execution extension. 2. Override OnBeforeTestlistStarted and OnAfterTestListCompleted. 3. Create a test list and run it remotely. Expected: OnBeforeTestListStarted and OnAfterTestListCompleted are called. Actual: OnBeforeTestListStarted and OnAfterTestListCompleted aren't called.
Seems obvious now, but I was tripped up by why my source bitmap and test bitmap were not comparing equal. It was because the Capture() grabbed the background color of the page and my source bitmap has a transparent background. Would it be practical to ignore transparent areas from the source to the test image?
When I record test with Test Studio each test starts application at test start and closes it after test run. I’m searching for an option that says “Reuse running app” or something similar. There is such an option for Web - 'RecycleBrowser'.
Multilevel nested data driven tests in a project (find attached). See structure below: Initial test -> runme - root (fail) --calls ''lvl1 - dd" which is datadriven lvl1 - dd --calls "lvl2 - dd (pass DD to lvl3)" which is datadriven lvl2 - dd (pass DD to lvl3) --calls "lvl3 - dd inherit" which is datadriven + inheritparentdatasource Expected behavior: lvl3 inherits lvl2 data and all tests pass Actual behavior: lvl3 inherits lvl1 data and doesn't find a match and all tests fail. A user expectation is that inherited data is only a level above in the nested structure. For reference in the project is also added an initial test "runme - root (ok)" which works fine since it calls a variant of "lvl1" that is not data driven.
In a *coded step*, I want to set a variable (SetExtractedValue) containing the machine name. Later, in the *Visual Steps*, I want to use an IF statement to interrogate the value of the variable and make a decision as to whether one block of statements should be run depending on the value. So, if in the coded step, the following lines are found: string sComputerName = System.Environment.MachineName; SetExtractedValue("RunningComputerName", sComputerName.ToString()); Then later, in a Visual Step, I want some include an IF statement with something like: IF (GetExtractedValue("RunningComputerName") = "BEDNERLT") do this block of visual steps ELSE do this other block of visual steps As a corollary request, allow a visual step to set the value of a variable that can be accessed by a coded step.
If you open the attached project you will find all the elements are under two page nodes with only the BaseUrl property being different. The goal is to merge the two page nodes. If you update the BaseUrl to be the same for both, then close (saving in the process) and reopen the project all the elements will be split all over again.
It would be nice if we implement a ScrollToMiddle feature in Test Studio. The reason for this is that we have ScrollToTop and ScrollToBottom, but sometimes when we have static elements for example static header or footer in a page the following problem is experienced: In a test if you want to click on an element that is scrolled to visible the element in question is getting under the static header or footer on the page and cannot be clicked.
I would like to see the name of the machine that ran the test list as part of the Manage Results dialog.
Every test we have has a Login test as step associated... so when creating a new test this always needs to be first. So lets say we have 400 tests, thats 400 checkmarks we need to make sure are unchecked before running a test list (dont want the login to trip twice)... so then lets say a handful of tests fail and we need to go back to editing them, we need to re-toggle that checkmark on the single test, and then remember to remove it later (which someone almost always forgets). It would be great to just select that step and have a property to say "Ignore in TestList" so when X test is added to the list, that STEP just gets ignored... This would save us so much manually work... no more checkmark toggles!
Steps to reproduce: 1. Connect a project to Team Foundation Service 2. Create a test list 3. Schedule it with option 'Get Latest' checked. Expected behavior: To execute the test list successful at the scheduled time Actual: An error appears that the source control server cannot be reached and test list is not executed.