Unplanned
Last Updated: 08 Aug 2016 17:18 by Scott
ADMIN
Ivaylo
Created on: 17 May 2016 11:14
Type: Feature Request
7
Token not detected as dynamic target
1. Create account for above website
2. Use Test Studio to capture traffic for a new User Profile in a Load Test
3. Navigate to http://ngauthenticationweb.azurewebsites.net/#/home
4. Log in with just created account
5. End recording when page loads after logging in
5. **Authentication token is generated in response of "http://ngauthenticationapi.azurewebsites.net/token" call
6. **Generated token is used in request of "http://ngauthenticationweb.azurewebsites.net/app/views/orders.html" call

Expected behavior: The token to be detected as dynamic target.
Actual behavior: Dynamic Targets button not enabled in Test Studio if this web traffic is used
3 comments
Scott
Posted on: 08 Aug 2016 17:18
To make things real clear because its not super clear from the topic - this is encountered when trying to create a load test within visual studio.  Hopefully some keywords about load testing and performance testing angular applications will help others find this request.
Brandon
Posted on: 06 Jun 2016 18:23
We are seeing this too. We are using angular and oauth, and we are experiencing similar issues where Test Studio does not recognize the token, anti-forgery, etc. 

Not being able to consume those important elements dynamically through the test has us blocked.
ADMIN
Daniel Djambov
Posted on: 24 May 2016 09:58
Telerik: will investigate if this is problem in our code or server specific configuration