Contributions
Re: Parameterization is not working in 3.8.1 in few scenarios
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.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes1CommentRe: Parameterization is not working in 3.8.1 in few scenarios
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.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes2CommentsRe: Parameterization is not working in 3.8.1 in few scenarios
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.3 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes4CommentsParameterization 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 observed is: the resource URL is not appended to the main URL when parameterization is used. Only when we hardcode the value it is getting appended. Kindly look into this at the earliest.1.4KViews0likes6Comments