Make Smart Assertion more useful with added features
Smart Assertions are very useful when having lots of data that need to be asserted. However currently there are a few issues that make it more difficult then it needs to be: 1. No Search Facility that allows quickly to jump to an item. 2. No conditional flow where assertions can be managed depending on some response details. 3. No facility to deal with lists that are unsorted and can be in a different order each time. 4. No facility to convert the Smart Assertions to Groovy Script which would make it useful as a tool to get a basic script with all the assertions that can be further edited to deal with special cases. Our responses contain hundreds of pieces of data that need to be evaluated. The Smart Assertions are great for quickly generating the assertions of a response but since we have many lists which don't arrive in a specific order, this does not work very well for us. If the Smart Assertions could recognise lists and pre-order them before assertion this would solve this problem and save us a lot of time. We also have an issue with repeated properties like for example version numbers that we only want to change once and then have it used in many places. However using a property only works as long as the data doesn't change. When data changes and we have to make a "Load from Transaction" again, those properties have to be added again. It would be nice to have something like an "Update from Transaction" that notices changes but doesn't overwrite existing items that haven't changed and preserves the properties being used. A differential dialog might be useful here when updating where we can see the changes, modify them if necessary or have them applied. Another great feature would be a conversion from Smart Asserts to Script. Other test applications that we use for desktop applications already can do this and it would be nice if SmartAPI also would be able to generate a script from the Assertions. This would help with situations where we need to have lots of special flows , loops and transformations of data but don't want to always have to write each assert from scratch.1.2KViews9likes2CommentsIssues and Feedback about Smart Assertions
Some issues and feedback about Smart Assertions after a day or so of using them. I would like to provide some hopefully helpful feedback on the newly introduced Smart Assertion. Please set the default name generated based on the type selected by the user. e.g. Smart Assertion - Metadata or Smart Assertion - Data The smart assertion does not handle simple text responses in the way that message content assertions do. The following response cannot be parsed by the Smart Assertion. Sure it isn't following good API design practice but it is a valid HTTP response and it is valid JSON data. HTTP/1.1 200 OK Date: Mon, 19 Jul 2021 21:43:03 GMT Content-Type: application/json; charset=utf-8 Content-Length: 29 Connection: keep-alive Server: Kestrel Cache-Control: no-cache Pragma: no-cache Expires: -1 "Your name has been updated." It doesn't seem all that smart to automatically include and enable in the metadata assertions data that is obviously going to change from response to response.Who thought that automatically adding response headers such as Date and Content-Length was a good ides? Date is guaranteed to change with every request. Content-Length is also likely to vary. This is not going to be an enjoyable experience for the novice user of ReadyAPI - "Use our Smart Assertion on your response, make your testing easier, you'll get a fail the moment you re-run the test".3.3KViews5likes10CommentsSmart assertion: ONLY populate FAILED assertion from received data
It would be very helpful to have the option to ONLY populate FAILED assertions from received data in the Smart Assertion. Now it's only possible to populate all data, which results in losing, for example, valid values asserted by property data.790Views4likes0CommentsDo not remove property when populating new values in Smart Assertion
When Smart Assertion is created property is used for some values in Valid Value column in Smart Assertion (ReadyAPI v3.9.2). Some values might changed in response so it is nice to use "Populate from Received Data". But it changes all values from response. It would be nice that there would be possibility to save/leave not changed properties.653Views3likes0CommentsRe-insert the Assertion HTTP
in version 3.9.0 there is a smartAssertion created that deprecates the HTTP assertions. As all of my testcases (a huge amount) have this assertion I'm not going to adapt them manually as this will take a huge effort to do so. No clue why Smartbear has deleted this assertion as I think quasi all of the testers are using this!? Please, re-install the HTTP assertions!1.8KViews3likes3CommentsUnable to read Kafka received messages using MessageExchange
Hi All, I have subscribed to a topic and i receive messages in the topic. When i add a script assertion to this step using MessageExchange like def response = messageExchange.getResponse() log.info response I am getting the following error Error in assertion script of the [Receive Message] test step: Cannot invoke method getResponse() on null object Am i missing to add something here?Can i read kafka received messages using messageExchange. Kindly help.Solved61Views2likes4CommentsSmart Assertion Conditions NOT Matches Regex
List of Smart Assertion Conditions 0. <, > , >= , <= 1. Equals AND Not Equal 3. Equals (one of) AND Not Equal (one of) 5. Exists AND Does NOT Exist 7. Empty AND NOT Empty 9. Contains AND does NOT Contain 11. Matches (regex) AND.... AND..... (!!) And... and..... and....!!! Uh..... what happened to NOT MATCHES (regex) ?!?!1.6KViews2likes3CommentsSmart Assertion on GraphQL Request Step
I was wondering why we can make a Smart Assertion on REST requests but can't make a Smart Assertion on GraphQL Request Step. We are currently using REST requests to test GraphQL as suggested and since the Smart Assertion tool is crucial in API testing for us but was wondering if there were any plans to support Smart Assertion in GraphQL requests? Seems like functionality of sending a REST request as a graphQL request is much more feature rich at this point in time.1.1KViews2likes0CommentsRamping up your usage of SOAP UI NG ? Check out our Free weekly Training webinar!
Hello all, Have you recently bought new Ready! API licenses and are about to kick start your API tests? Register here for our Free Weekly interactive Webinar, Next one is on the 7th of September( day after Labor day) What to expect? Advice on getting up and running on your SOAP and REST projects Hidden gems within the tool that you may not uncover on your own Personalized question-and-answer with our API experts If you have 10+ users and would like to get your users on-boarded, please reply to this message and I'll be in touch. Cheers, Katleen B Snr. Customer Success Advisor EMEA kbb(at)smartbear.com1.4KViews2likes0Comments