Taz
Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: How to stop "assert" to display junk at the end of a failed assertion message?
Not sure how this answers my question. The problem is that I try to avoid extra work to assert a variable having to do anything. Groovy seems to be strange that it treats the original variable different when it is copied into another. As you can see from the examples I have given, it is both times the exact same test. The only difference that when I use the original variable for assert, it also displays a lot of junk after it, but when I copy it into another variable first and then do an assert, it doesn't. I just wonder if there is something that can be done to stop this behaviour.769Views0likes1CommentRe: Refactoring API definition does not properly update the version in the spec in ReadyAPI.
Not sure if it relates but we had an issue where parameterised api's did not have parameter names that match exactly with the declared variables. For example if the parameter is .../{testId}/... but the property behind it is TestId or just id, then ReadyAPI failed to import or update the APIs from swagger.515Views0likes0CommentsHow to stop "assert" to display junk at the end of a failed assertion message?
There is an annoying side effect when using "assert" in a groovy script to verify items from a property. It often displays too much junk at the end of it: Assertion failed: assert ep.Flow == sp.flow | | | | | | '0' | | 0.0 | | ['startDate':'2020-09-02T15:30:00', 'endDate':'2020-09-02T16:24:00', 'flow':0.0, 'flowUnit':['unit':'', 'flowTimeUnit':'Unspecified', 'version':'2.5.0'], . | false EP@66f5016c error at line: 10 If however the value is first copied into another variable, then it displays correctly. def f = sp.flow assert ep.Flow == f; Assertion failed: assert ep.Flow == f | | | | | '0' | 0.0 | false EP@eeab99e error at line: 10 However, this bloats the code unnecessarily. Is there a better way to deal with it?946Views0likes5CommentsRe: How to best assert unordered results?
Our APIs return large lists of data that contain other lists of data that are taken from a database. The order is never guaranteed because of parallelism where data is pushed out as soon as they are available and also because the database itself returns data with no guarantee of order. This means that the root data can be unsorted as well as the leaf data. Right now to ensure that all data are asserted correctly it is necessary to do it in a script where we either can pre-order the results and evaluate them one by one or make conditional statements where we check the id and evaluate correspondingly. Some fields are expected to change over time like version numbers, we therefore evaluate them against a single property that we can change with each new version. Other fields do change at times during development and we therefore need a way to quickly adjust for that. If Smart Assertions would recognise Lists they could do the ordering based on a specified key. This would be ideal but unfortunately this feature doesn´t exist yet. They could be a little bit smarter in my opinion 😉552Views0likes0CommentsRe: How to iterate throw Excel data in a groovy script?
Thank you for the reply. I was aware of the data-driven concepts but they didn´t address the issue of me wanting to use the Excel Data within a groovy script. From your answer I guess the only way is to use a third party component like SoapUI. I will look into this.753Views0likes0CommentsHow to iterate throw Excel data in a groovy script?
I created a data source with Excel and want to use it in a groovy script. Using "Get Data" I can get individual properties but it appears to only pick out individual data properties from the last row. I would like to get the whole sheet as an object, either of rows and columns or a list of objects. How can this be best achieved?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.3KViews11likes2Comments