Forum Discussion

ihorstep's avatar
ihorstep
Occasional Contributor
4 years ago

Smart Assertions - Metadata and case sensitive header names

Smart Assertions - Metadata and case sensitive header names   I've recently have found out that smart assertions seems to be case sensitive to header name. For example there are two web-servers. Bo...
Assertions
ihorstep's avatar
ihorstep
Occasional Contributor

Yes, also added the screenshot to the previous post.

  • ihorstep's avatar
    ihorstep
    Occasional Contributor
    4 years ago

    Thanks for the reply mattb.

    Created support ticket.

    • JoostDG's avatar
      JoostDG
      Frequent Contributor
      3 years ago

      I believe this has been "fixed"...

      I see in version history 3.20.1 (https://support.smartbear.com/readyapi/docs/general-info/version-history/bugs-fixed-in-ver-3-20-1.html) :

      • The Smart Assertion was case-sensitive when checking header names, so it could not find headers written using different cases. (RIA-18797)

       

      While I applaud SmartBear for listening to this community and fixing issues raised by it's users, this fix did have a nasty side-effect for me... 

       

      I updated my ReadyAPI version, ran my tests locally (on Windows, everything ran fine) and checked them into my repo. I noticed a lot of track changes, all with the same change: The Smart assertions metadata elements path got their upper casings changed to a lower casing:

       

      Next day, when my tests ran in the pipeline (on a Linux agent with older readyAPI version 3.10.2) I got a ton of errors, all saying:

      <h3><b>POST dossiers Failed</b></h3><pre>[Smart Assertion - HTTP201 and application/json] Smart Assertion failed:
      Field 'Content-Type' does not equal (case-sensitive) 'application/json'; received: ''
      Status: FAIL

       

      I guess when I update the ReadyAPI version on the agent it will get solved, but that's not immediately available to me (have to request other team to do so)

      So either I am stuck for a few days with a failing test pipeline...or I delete the smart assertions metada... I chose for the latter.