cancel
Showing results for 
Search instead for 
Did you mean: 

How to change Assert Namespace definition per Environment?

Highlighted
Occasional Visitor

How to change Assert Namespace definition per Environment?

Hello!

  We have about 10 different test environments, and using the Environments setting works just fine for the Endpoints. However, the property transfers and asserts do not dynamically change per environment, so they keep trying to "declare namespace m='http://testurl.01:5050/Service';" when it might really be testurl.05 instead.

 

 Is there a way to create an Environment-level custom property to specify the namespace URL?

1 REPLY 1
Highlighted
Community Hero

Re: How to change Assert Namespace definition per Environment?

Usually namespaces are same irrespective of different environments. But, can't deny if there is possible to have different.

It is not possible to have a variable in property transfer step.

Like possible to achieve if groovy step is used.

However, there is work around to ignore namespaces

For eg:
xpath with namespace prefix : "//ns1:element1/ns2:element2/text()"

Can be used
"//*:element1/*:element2/text()"


Regards,
Rao.
New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors