Forum Discussion

ARR's avatar
ARR
Occasional Contributor
4 years ago
Solved

Parameterizing Property Checkpoints in keyword test

In "Keyword test" i want to use a parameter for a "Property Checkpoint". Here you can find the instructions: https://support.smartbear.com/testcomplete/docs/testing-with/checkpoints/property/parameterizing.html#KDT (Step 2.)

 

According to the documentation it should work.

 

But I don't get an [...]-option under "Values". When I double click on the cell, only the "Edit Property Checkpoint" window opens, which does not give me the possibility to set a parameter, only a hard-coded value.

 

Is there a solution to this?

  • You need to click in the field, once... single click... to select the field.  Then the button will show.

  • hkim5's avatar
    hkim5
    4 years ago

    yup, anywhere within that value field in that row, give it a single click and wait a second! you should see the ellipses appear at the far right side of the value column, and once you click on those three dots, you should gain access to the operation parameters. You can do this for any other operation other than a property checkpoint in order to parameterize that step as well.

5 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor

    Once you create the checkpoint through the wizard as you did, you need to go back and re-edit the property checkpoint operation in your keyword test, specifically, click on the "..." button that is available in the Values field in your keyword editor

     

    • ARR's avatar
      ARR
      Occasional Contributor

      Thank you for your answer. But as I have already written:

       

      "But I don't get an [...]-option under "Values"."

       

      Screenshot:

       

       

       

       

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor

        You need to click in the field, once... single click... to select the field.  Then the button will show.

  • ARR's avatar
    ARR
    Occasional Contributor

    Thanks for the solution. Now I can get back to work.