Table Checkpoint - How to ignore numeric differences past the 10th decimal place
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2010
07:12 AM
09-27-2010
07:12 AM
Table Checkpoint - How to ignore numeric differences past the 10th decimal place
Hi there,
A table in our application stores numbers out to as far as 20 decimal places. (Under the hood it needs to.) Sometimes there are numeric differences 10+ decimal places out. I want TestComplete8 to ignore those differences.
I tried editing an individual table checkpoint value and inserting a wildcard (0.123456789012345 became 0.1234567890* ) but * was recognized as an asterisk, not a wildcard.
How can I set up a table checkpoint so it ignores differences past the 10th decimal place?
Thanks,
Chuck
A table in our application stores numbers out to as far as 20 decimal places. (Under the hood it needs to.) Sometimes there are numeric differences 10+ decimal places out. I want TestComplete8 to ignore those differences.
I tried editing an individual table checkpoint value and inserting a wildcard (0.123456789012345 became 0.1234567890* ) but * was recognized as an asterisk, not a wildcard.
How can I set up a table checkpoint so it ignores differences past the 10th decimal place?
Thanks,
Chuck
7 REPLIES 7
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2010
07:03 AM
10-01-2010
07:03 AM
Hi Chuck,
Currently, there is no way to do this. You will have to enumerate table cells and write the needed comparison logic yourself. However, I've registered your request in our DB as a suggestion. Thank you.
-----
Alexander
Customer Care Manager
Alexander
Customer Care Manager
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2010
07:38 PM
10-03-2010
07:38 PM
Hi Chuck,
Meanwhile as a workaround and depending on the database server you are using, you may consider creation of the helper stored procedure (SP) that will wrap your actual SQL statement and return data formatted with the precision that you need. Then you may save the initial SP output as a checkpoint and use it for the test.
Meanwhile as a workaround and depending on the database server you are using, you may consider creation of the helper stored procedure (SP) that will wrap your actual SQL statement and return data formatted with the precision that you need. Then you may save the initial SP output as a checkpoint and use it for the test.
Regards,
/Alex [Community Champion]
____
[Community Champions] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Champions]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Champion] signature is assigned on quarterly basis and is used with permission by SmartBear Software.
https://community.smartbear.com/t5/Community-Champions/About-the-Community-Champions-Program/gpm-p/252662
================================
/Alex [Community Champion]
____
[Community Champions] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Champions]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Champion] signature is assigned on quarterly basis and is used with permission by SmartBear Software.
https://community.smartbear.com/t5/Community-Champions/About-the-Community-Champions-Program/gpm-p/252662
================================
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2014
12:17 AM
11-28-2014
12:17 AM
Has there been any progress on this since 2010?
I am also looking for a way to wildcard data in table checkpoints.
I am also looking for a way to wildcard data in table checkpoints.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2014
06:42 PM
11-30-2014
06:42 PM
Hi Paul,
It's still under the development. I've added your vote to the suggestion.
In TestComplete 10, there is a way to exclude a cell or a row from the comparison. Check whether it works for you.
---------
Tanya Yatskovskaya
SmartBear Community and Education Manager
Tanya Yatskovskaya
SmartBear Community and Education Manager
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2014
12:24 AM
12-11-2014
12:24 AM
Hi,
I am also looking for a way to wildcard data in table checkpoints.
Like:
14-300-12345678
**-300-12345678
Regards,
Kristijan
I am also looking for a way to wildcard data in table checkpoints.
Like:
14-300-12345678
**-300-12345678
Regards,
Kristijan
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2014
10:48 PM
12-14-2014
10:48 PM
Hi Kristijan,
Right now, to accomplish your task, you need to create a customer comparison function that will compare each cell of the table with the desired value.
As for the Table Checkpoints, I've added your vote to improve the comparison algorithms.
---------
Tanya Yatskovskaya
SmartBear Community and Education Manager
Tanya Yatskovskaya
SmartBear Community and Education Manager
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2019
05:53 AM
05-01-2019
05:53 AM
Please add my vote for this feaure.
Either ? and * wildcards,
or Greater Than / Less Than by absolute or percentage for numerics
or something similar to the cmpCompare function in the If/Then statement would be sufficient.
Can you give me a hint what the custom code might look like? I've found the Compare Properties function but it's kinda painful to set up a separate check step for each cell in a grid.
