Forum Discussion

vijita's avatar
vijita
New Contributor
4 years ago

Parameterization is not working in 3.8.1 in few scenarios

Hi Team, I have been trying to automate a few scenario's and there are interdependent steps where parametrization is required. But the parameterization is not working in these cases. Another issue ...
Data-Driven Testing
REST
Scripting
vijita's avatar
vijita
New Contributor
4 years ago

Ex: Multiple test suites are present and information from the 1st suite should be used in the second one.

GET call results in first suite to be used by the POST call in the second suite.

The parameter here is not being converted to its value. the steps followed is Get data and then select the value from the GET response.

it remains like:  " "${GET Activity#Response#$['objectId']}", even after running the scripts in order.

  • nmrao's avatar
    nmrao
    Champion Level 3
    4 years ago
    - Have you check the the link given in the pervious repply?
    - Have the test cases independent, which helps to achieve automation. But you are trying to have dependency between the suite. Please revisit and make them independent.
    - Avoid spaces in the names of suite / test case / steps while providing a way to identify and readable like Camel case
    - Would it be possible to create a sample project to demonstrate the issue?

    • vijita's avatar
      vijita
      New Contributor
      4 years ago

      Yes. I have tried the what you have mentioned. Sure i will be able to demonstrate the same in a sample scenario.

      Let me know when we can have this meeting setup.

      • vijita's avatar
        vijita
        New Contributor
        4 years ago

        Hi Rao, 

        have tried changing all the names to camel casing(Test Suite, Test case and Test steps) and it started working. but there were few scenarios where it worked even without implementing the camel casing. Please take a look into the issue anyhow so that it doesn't depend on the naming conventions.