Comparison Rules
Enterprise level automation tools are claimed to be suitable for a wide range of users, including non-technical, not programming, like some testers and business analysts. To support such types of users, tools offer a variety of pre-defined, built-in components.
The first problem is in availability of comparison rules. Most of the tools offer only simplistic “Is Equal” rule, and support numeric and string formats. Some, more advanced, support rules like “Less Than”, “Greater Than”. But none of them (per my knowledge, I’ve seen all from “Top 10″ chart) supports One-To-Many and Many-To-Many types of relationship in comparison.
And yet these types are the most desired as they make automatic comparison much more flexible, and more realistic to the live testing performed by a qualified specialist.
The second problem is test data. Numeric and string formats are not everything. At least, date/time format should be supported. Both actual result and expected result should be stored as a single, vector, or matrix values with the help of Data Model.
Within the scope of this project Albert Gareev defines logic and implements extended set of comparison rules for automated checking. Source code is supplied.
Disclaimer
All the content referenced below does not copy or represent a commercial solution. This is a collection of ideas and implemented concepts, research and investigations results. If you use it, you use it at your own risk.
Copyright
Please make sure you have read, understood, and agreed with Copyright and Content policy.
Unauthorized use and/or duplication of materials from this blog without express and written permission from this blog’s author and owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Albert Gareev with appropriate and specific direction to the original content.
Unless otherwise stated, all code examples, functions, function libraries, workarounds, etc. are created by Albert Gareev, and are copyrighted.
You may use them to design, develop and test your own software. You may modify the original source code as you need.
However, you must ensure that full and clear credit is given to Albert Gareev with an appropriate and specific direction to the original content. If your Employer’s policies restrict that then you may not use the source code provided.
Rationale
Built-in verification in Testing Tools – too simple, too narrow
Comparison: One-to-One Relationship
1-1 Comparison: isValueEqualOrLess
1-1 Comparison: isValueGreater
1-1 Comparison: isValueEqualOrGreater
1-1 Comparison: MatchIn / MatchFor
Comparison: One-to-Many Relationship
1-N Comparison: isValueInRange
Comparison: Many-to-Many Relationship
