Ask a Question

Assertion type Message Content Assertion deprecated, will and when will it be removed?

SOLVED
kostel00
New Contributor

Assertion type Message Content Assertion deprecated, will and when will it be removed?

I notice in ReadyAPI that assertion type="MessageContentAssertion" is deprecated, will and when will it be removed?

I have about 900 assertions of type="MessageContentAssertion" in my test projects and am wondering if there's a deadline and if so, what that deadline is to replace them by none-depricated assertion types.

3 REPLIES 3
richie
Community Hero

Hey @kostel00,

Someone asked a similar question relating to the http status code assertion type which is also being deprecated. There are actually several that will be deprecated and moved over to the Smart Assertion functionality if im remembering correctly.

The Smartbear representative didnt provide a deadline date, but id guess (considering other software/libraries ive used that have been deprecated) it would be unusual to remove the functionality within say a year of declaring the deprecation.....especially in this case.....if i remember correctly there were a number of assertions that are being migrated into the Smart Assertion functionality.

Every users in the same situation im afraid. Ive multiple projects that will likely take weeks before ive sorted them out.

Cheers,

Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta

ok, when it's supposed to be replaced by the Smart Assertion functionality, does anyone have a xslt to automatically replace the Message Content Assertion by Smart Assertions in the test project xmls? This would save us a lot of time...

kostel00_0-1664538716280.png

"Message Content Assertion" assertion type is not deprecated anymore as of ReadyAPI 3.41.0, so "problem" solved...

 

cancel
Showing results for 
Search instead for 
Did you mean: