cancel
Showing results for 
Search instead for 
Did you mean: 

Definitions have not been actually updated

SOLVED
Contributor

Definitions have not been actually updated

Anyone encountered such issues:

Manually updated source file (.json) of REST, and updated definition in SoapUI, new change have not been reflected on SoapUI?

 

For example:

As defined the same parameter in Path (i.e: /account/{userID}/) and Header, SoapUI cannot display parameter which defined in path due to conflict with that of Header. Now manually remove conflicted "parameter" in source file, and update definition in SoapUI. There is no any change for that.

 

Temporary solution: Save as those testSuites which impacted by updated definitions, delete original definitions from project, and re-import updated definitions, then import testSuite again. the change is reflected now.

 

ReadyAPI version: 2.4

 

Thank you

 

/Aaron

1 ACCEPTED SOLUTION

Accepted Solutions
Contributor

Re: Definitions have not been actually updated

Hi @Nastya_Khovrina , I found a solution (write a script to update source file) to deal with it. the root cause is that SoapUI won't remove existing "parameter" if you delete conflicted parameter in source file. I renamed the conflicted parameter name instead of deletion in source file, then update definition, it's OK now.

 

Thanks @Nastya_Khovrina 

 

BR,

/Aaron

7 REPLIES 7
Moderator

Re: Definitions have not been actually updated

Hi aaronpliu,

 

Unfortunately, currently, there is no way to add both values: a parameter and header if they have the same name. We have a corresponding feature request to improve this behavior. 

 

In the meantime, you can add your Header parameter as a header in the "Headers" tab:

ReadyAPI_2019-03-13_10-49-53.png


Anastasia
Customer Care Team

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.
Contributor

Re: Definitions have not been actually updated

Thanks @Nastya_Khovrina .

Yes, I can add "parameter" in Headers tab and do it for other parameter, like "Cookie", "Content-Type"...etc.

However, all of parameters are shown in "Request" panel with different "style and level" when import endpoints, right?  Style for "Query" as query parameter, "TEMPLATE" is part of path, "Header" is for request header... I always need to take "parameter" (style is "TEMPLATE") and ignore "parameter" in Header if they are the same name.

"parameters" in request panel are "Custom Properties", "Headers" tab are another key-pair. What's difference for them?

 

Anyway, how can I update definition and don't worry about missing "parameters" if there are the same?

I can hardly update them and have to manually maintain definition change in SoapUI. That is not expected behavior, there are so many test cases created and referenced those endpoints already.

 

Thanks,

/Aaron

Moderator

Re: Definitions have not been actually updated

Hi Aaron,

 

There is no difference between the "Header" parameters and headers which are defined in the Headers tab.

ReadyAPI_2019-03-14_13-07-07.pngReadyAPI_2019-03-14_13-07-29.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Unfortunately, there is no workaround except for the provided one.


Anastasia
Customer Care Team

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.
Contributor

Re: Definitions have not been actually updated

Thanks @Nastya_Khovrina .

Let's skip the topic of parameter of Header.

Can we talk about definition update? I don't know why definition was not updated even if I changed source file?

I manually copy the source file (.json) from server, and put it in my local. as conflicted parameter name (said above), I had to remove one, and updated definition in SoapUI. the changes were not reflected in SoapUI, and seems it keep the same as before.

Did you repro such issue?

 

Thanks,

/Aaron

Moderator

Re: Definitions have not been actually updated

Hi Aaron,

 

To reproduce the issue we will need your old and new definition files. 

Also, please clarify what changes were not reflected.


Anastasia
Customer Care Team

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.
Contributor

Re: Definitions have not been actually updated

Hi @Nastya_Khovrina , I found a solution (write a script to update source file) to deal with it. the root cause is that SoapUI won't remove existing "parameter" if you delete conflicted parameter in source file. I renamed the conflicted parameter name instead of deletion in source file, then update definition, it's OK now.

 

Thanks @Nastya_Khovrina 

 

BR,

/Aaron

Moderator

Re: Definitions have not been actually updated

Hi Aaron,

 

Thank you for sharing the solution with us!


Anastasia
Customer Care Team

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.
New Here?
Join us and watch the welcome video:
Top Kudoed Authors