locked
Request failed: Context parameter '$HIDDEN0.ctl00$ContentPlaceHolder1$hdIsPlannedOutcome' not found in test context. RRS feed

  • Question

  • hi

    in my webtest i m getting this issue how to resolve it pls help me out.

    Friday, July 11, 2014 11:32 AM

Answers

  • Hi,

    For this issue, probably it is because your previous request where the extraction rule is used didn’t return the expected response. You should try to investigate on the previous request if something wrong happened there.

    It is also likely that there are some dynamic variables, such as a session id, that are hard coded in your requests and you need to modify your requests to not hard code these values.

    Here is an article offer detailed solution for this kind of issue that you can refer to:

    How to debug a Web Test

    Best regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, July 14, 2014 6:35 AM

All replies

  • Hi

    Essentially when you recorded your webtest a hidden field called "ctl00$ContentPlaceHolder1$hdIsPlannedOutcome" which was being passed as a parameter.  Now for some reason this is not there probably it has changed it's name as it was originally a place holder.  Alternatively it might be failing to render if you are running it under high load.

    Bearing in mind Hidden fields are collected at runtime. rather than having a dedicated extraction rule for each field as with other forms of dynamic parameters.

    HTH

    Friday, July 11, 2014 1:51 PM
  • Hi,

    For this issue, probably it is because your previous request where the extraction rule is used didn’t return the expected response. You should try to investigate on the previous request if something wrong happened there.

    It is also likely that there are some dynamic variables, such as a session id, that are hard coded in your requests and you need to modify your requests to not hard code these values.

    Here is an article offer detailed solution for this kind of issue that you can refer to:

    How to debug a Web Test

    Best regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, July 14, 2014 6:35 AM