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.
It would be nice to have the story board capture subtest screenshots instead of the "Test Step" placeholder. It would be fine maybe to watermark the screenshots with "Test Step," but still show the screens for reference.
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.
Currently the request body supports only plain text. Add other formats like form-data or x-www-form-urlencoded.
I would like to have official support for Atlassian's Bamboo CI tool. This is a very heavily used CI environment, and although we can still call from the CLI, it would be nice to have baked-in compatibility.
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.
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
All tests under a single project in Test Studio should be in one and the same namespace. If we use different namespaces Test Studio changes the namespace to the one set in the project settings. There should be an option to use different namespaces.
Deleting steps delete elements in the Elements Explorer that are already used in Coded steps. Steps to reproduce: 1. Create a simple test that includes a step that selects one element. This element will be visible in the Elements Explorer. 2. Add a coded step that uses the same element. 3. Select the the first step that adds the element in the Elements Explorer and delete it. Actual: Compilation fails. The element that is used in the coded step is no longer in the Elements Explorer. Expected: Test passes .
Currently, the selected browser will open automatically before the first steps are executed. If there was a way to prevent this from occurring until after a pretest script is executed that would be a HUGE plus. Much the same QTP allows you to just execute a script and doesn't require the browser even be open and later you InvokeApplication to start the web based scripting. For instance if I want to change my hosts file to point to a specific DEV box I need to execute a batch file to update my hosts. But if the browser is open first then it's going to wherever it wants really. The only way around I've found is to execute the first cycle with a blank row to skip to the next iteration of the script but at the end clear and go to next hosts.
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
There should be a way to run only selected test cases from a test list. If few test cases fail in a list, then we should be able to select those test cases and run only selected test cases.