R de Ronde

Option to ignore a test during testexecution

It would be very welcome if there is an option to be able to ignore a test during testexecution. For example when you have a suite with tests and you know that one test will keep failing for some time (api work in progress etc), after running the suite, the suite gets a red dot while the others tests have passed.
Idea by R de Ronde Status: Reviewed Comments: 2 Last update: 2017-02-27T08:27:08 by Oleg Georgiev
Wesley Kenis

test studio

I try using OAuth2.0 and fill in all required data (client & secret)

1. I can't set the grant type to password
2. the request just ignores my entries and keeps using Basic with whatever you think is my password since there is not even a posibility to edit the test variables

3. update request places a Basic authorization tag instead of the OAuth2 I filled in

for an alpha version this would be ok, but for a Beta this should have been tested before release
Feedback by Wesley Kenis Status: Reviewed Comments: 1 Last update: 2017-02-20T15:13:45 by Oleg Georgiev
R de Ronde

Set variable does not get set since last update


Yesterday I updated Telerik API to version 2017.1.207.0 and I now seem to have trouble getting the Bearertoken set using Set Variable.

The Set Variable step is defined as

Source: Body JSONPath acces_token
Variable: Bearertoken
Convert to: none
Target Level: Test

which worked fine with the Response Body in an earlier step that returned the AccessToken


which resulted in setting the Bearertoken as "xxxx"

Since the update the Bearertoken does not get set (=empty). This is probably due to a new validation of the JSON path: "The path is not a valid Jsonpath" ?
However, if I change JSONPath to $.access_token the bearertoken still does not get set (=empty).
Please advise on how to get this working again. It blocks running my testcases.
Feedback by R de Ronde Status: In Development Comments: 3 Last update: 2017-02-20T07:36:46 by Oleg Georgiev
Alexis Coles

base-url not recognised

I have just downloaded the latest version 2016.3.928.0 (why cant i copy this version number from the help about menu?).

have set base-url under project to http://localhost:59093 and added a test that calls {{base-url}}/SxWinService?environment=uat1&serviceName=*Entity* however when run it calls http://localhost:5000/SxWinService?environment=uat1&serviceName=*Entity*

At least it did last few times I ran it, but not this time, very strange I don't think I have done anything. maybe saved the project, hmmm. weird. Anyway there is defo something strange about this.

Very much like this https://feedback.telerik.com/Project/182/Feedback/Details/205353-base-url-mostly-defaults-to-localhost5000

which seems to be signed off, but there is something weird with it. Maybe try testing on a fresh box...
Feedback by Alexis Coles Status: Completed Comments: 2 Last update: 2017-02-10T16:30:58 by Oleg Georgiev
Patryk Patkowski

TS needs to be restarted after variables are set

1. Create new variable
2. Write test with variable
3. Variable does not exist until TS is restarted

11:35:17.238 [ERROR] [FAILED] | | 'POST {{variable}}' [80 ms] [3kIGJsPrSkMyCmJcS4Lcm7] 'Value cannot be null.
Feedback by Patryk Patkowski Status: Completed Comments: 1 Last update: 2017-02-10T16:28:31 by Oleg Georgiev
Peter Heijligers

Authorization using the bearer token

In our Web API authorization we make use of the bearer token. Is it possible to use the bearer token in Telerik Test Studio too, or is this a new feature request?
Feedback by Peter Heijligers Status: Completed Comments: 5 Last update: 2017-02-10T16:21:57 by Oleg Georgiev
Kieron Fairgrieve

Verifications & Conditions using xpath

Would be nice to be able to do XPath to select item to Verify or Constraint against
Feature Request by Kieron Fairgrieve Status: Completed Comments: 3 Last update: 2017-02-10T16:17:31 by Oleg Georgiev
Anton Dobrev

Ability to invoke requests as cross-origin and over HTTP(s)

Very frequently I need to test a web services behavior when:
- Simulating a cross-origin request
- Simulating the same request by toggling HTTP/HTTPS

For both use cases I would like to be able to:
- Determine the option with a simple select/check
- Have a visual indication whether the option is selected or not on a request level
- Ability to enter options - for example, a request should fail over HTTP, a specific domain is not allowed for cross-origin request

Thanks for your consideration.

Feature Request by Anton Dobrev Status: Completed Comments: 2 Last update: 2017-02-02T12:24:22 by Oleg Georgiev
Oleg Georgiev
Team Member

Allow http request timeout to refer to a custom variable

I am logging this feature request on behalf of Eugeniy Gorbovoy.

Currently the timeout setting of http requests allows only numeric input and defaults to 2000 ms when left empty. The initial plans are to implement a global project-level setting for timeout that all http requests should inherit (unless locally overwritten). (I hope we will have it delivered in some of our releases in the near future.) This should handle most cases when users want to manage the timeout from a single place instead of manually increasing it for every new http step they create.

Still the idea for accepting a reference to a variable seems appealing since some users might prefer to have several "tiers" of timeout rules across the test project and manage them using variables. Any comments and shared use-cases are appreciated.
Feature Request by Oleg Georgiev Status: Reviewed Comments: 0 Last update: 2017-01-30T07:36:14 by Oleg Georgiev
Eugeniy Gorbovoy


Need https support
Feature Request by Eugeniy Gorbovoy Status: Completed Comments: 3 Last update: 2017-01-25T16:26:11 by Oleg Georgiev
Displaying items 1 - 10 of 66