the part after # is the fragment identifier and will not be sent to the server as part of the URL. Javascript on the client will take care of this part and move on to the specific section specified by Id. However, I am interested to know if it is possible to simulate similar actions using a web performance test. Basically, the actions should be: 1) sending a request to the server and receiving a response, and 2) after receiving the response, go to the section indicated by #. The next step will be on the client side, but I wonder if it is possible to simulate the second part at the request of visual studio web performance. If anyone has an idea, please let me know. thanks
source share