I do not see any feedback items that talks about the updates to test studio and integration of test studio and visual studio 2013. I would assume that this would most likely be in a major release.
As I know some Chrome extensions have checkbox "Allow access to URL address files". It allows Chrome to navigate to local files during the test execution.
Currently the request body supports only plain text. Add other formats like form-data or x-www-form-urlencoded.
Often tests require dynamically generated data like a random value that could provide the ability to generate unique test input (like unique user names). One way is to generate random strings/numbers. Another options is to take the current date and time from the system. Aside from randomness, it might be useful to be able to access environment variables related to the operating system. Any comments with other use-cases are appreciated.
It would be a nice addition if telerik test studio (+scheduler service) was able to also record fullscreen video (swf/mp4 etc) of any failed tests. I currently have implemented a DIY IExecutionExtension plugin that takes care of this. It works quite nicely. How it works ? Upon test-start it will initiate a fullscreen recording using the SDK from techsmith (Jing SWF video recorder.dll). It will then record a video until the test finishes. If the test fails it will keep the video, if the test succeeded the video will be discarded. failed tests are saved in this file naming pattern: [user defineable path]+[testname]+date.swf example: C:\temp\DMS - 2013-06-04.09.19.swf failed tests within testlists are saved in this file naming pattern: [user defineable path]+[testlist name]+date \ [testname]+date.swf example: c:\temp\IsAlive test - critical sites - 2013-06-06.09.27\Log ind på Agromarkets.dk - 2013-06-06.09.29.swf I have then shared the c:\temp folder and modified the schedulers email layout to include this path. So any testers can easily watch those videos and see what happens just prior to the failure. Any chance of having some builtin feature like this in telerik would be awesome and an alternative to the normal screen capture features that we already have ? My custom plugin works nicely and it should make our team here able to more quickly be able to identify why a given test fails. Sometimes those stacktraces are a bit voodo for non coders :) regards and thanks for listening :) Elo
I would like to see the ability where after running a test list you can select all failed test (e.g. with a checkbox) and re-run them. This is extremely helpful and will save a lot of time.
Add a test as step. Double click the step. This navigates you to the other test. Nice to have: 1) back button - go to the previous test 2) forward button - opposite of back 3) up one level button - go to the parent, no matter which test is the previous one
Schedule test list: Email settings Persist for the project. Currently you must fill out the attachment type, who the email is sent to, title, ect. Currently If you close out of the project these are lost. If you are in a project and do not close the project, it retains the settings. this should persist through the project.
This would be useful as an "object oriented" use of test steps. The goal would be to reuse test steps for different data inputs and website global settings for our website testing. Another benefit of the test bind data being set outside of the test step is that source control would be relatively unaffected by the modification of data input into the bound table. Considering using MS Access to have tables bound to specific test steps and deleting records and appending new records prior to test step execution within a system test (some are simple functional test and others are more complex system tests and setups). In our proposed implementation a 'coded step' would need to be executed prior to the test step to clear and append the table which is bound to the test step. Btw, many of the test steps are bound to a table with a single record. Perhaps allow instances of test as steps to be inserted in a test case with instance specific data binding. This may not be ideal but it should work.
scheduling test lists: make the default time in the future. Currently the time is default to current time, so it will not run because that time will have passed by the time you have completed the schedule. Please make the default time 5 minutes in the future
Please consider adding the UI functionality in Test Studio so users can be able to drill up/down in tests as steps (sub tests) and then go back in the parrent test. Currently when you double click on a test as step, Test Studio opens the test steps, but there is no option to go back in the parent test. The only workaround is to the Project Tab, and then open the parent test. It would be much easier and faster if you have back and forward buttons, or Up and Down.
I find that I'm spending a TON of time having to jump back to the "Test" tab, then dbl-click into another test...time I'd like to get back :) Can we have an optional pinnable nav bar like in VS that gives me a list of tests so I don't have to keep jumping back to the tab...I want to see this on every screen. Or maybe even just a "Top 5-10 Recent tests" dropdown or list or something...
Currently, the if...else statement can only be based on a verify statement i.e. can only be based on the state of the UI e.g. an element is visible or not. But my tests need to execute a data-driven if...else statement, like this pseudo-code: if (data-driven property X) then verify that screen element Y exists. else verify that screen element Y does not exist. I want to be able to do this in order to write a testcase which checks, for several different user accounts, that they have the appropriate navigation links available to them in my web app.
Currently when Test Studio wants to scroll an element to make it visible (such as when SimulateRealClick or SimulateRealTyping is enabled) Test Studio will always, and unconditionally, scroll the element to the top. This causes problems for a few applications that have a static UI element, the target element ends up being scrolled underneath this static UI element. It would be helpful to have a global setting which controls whether the target element is scrolled to the top or the bottom of the browser window. The parameter is available in the API, just need to expose it as a step setting, or a global setting so that customers aren't forced to convert the step to code and override the default behavior, which can be time consuming when there are lots of steps that this must be done on.