Forum Discussion
Hi AlexKaras ,
Yes, I tried the exactly same thing to manually delete those symbols but in the end Table Checkpoint failed after I execute the test.
 
I have go through the Tools>Options>Engines>Stores, the 'Update Table elements' checkbox is unchecked.
Hi,
Checkpoint result reports visually same values for the stored and actual data. (Unless I overlooked something)
This makes me think that actual data in the database contain some non-printable symbols which are not displayed but are considered during comparison and cause compare to fail.
What if you try to query data from the database just for this problematic row and cell and also query length of cell's data. If the returned length differs from the length of displayed data this will mean that cell data indeed contain some non-printable symbols.
Whether this is correct for your tested application/database will be a question to you.
Whether this is expected behavior for the checkpoint will be a question to Support.
If the returned data length matches the length of displayed data then I have no better idea at the moment but to create Support ticket via the https://support.smartbear.com/testcomplete/message/ form.
- Josh_1473 years agoContributor
Hi AlexKaras
This is the update regarding this issue.
I had asked the Support, after they pasting the non-printable character into a text field in their sample table app reproduces the issue.
They had reported it to the developers and it will be fixed in one of the future releases based on the general backlog order.
- Josh_1473 years agoContributor
Hi,
Yes, they didn't mentioned the method to fix it. Sorry about that.
- Josh_1473 years agoContributor
Hi,
I have tried the following steps to check the length of the string:
1. Using table checkpoint to retrieve the table data and copy the string in Preview tab.
2. Select all the string, right click and checked on the 'Show Unicode control characters'.
3. There is no new character showing.
4. Copy the whole string and paste into a C++ online compiler. This is the result.
5. The total string length is 41, included the 2 red dots. While pointing on the red dot, it shows /u1d
By referring to here, HTML Entity (decimal) is  (similar to what TestComplete saved in tc.Tbl) while C++ is "\u1D" (quite similar compare to \u1d, the red dot).
So, it should be a non-printable character and considered during the comparison with the tc.Tbl file that I manually edited.
- AlexKaras3 years agoChampion Level 3
Hi,
So, if I got your results right:
-- Data to be compared contain non-printable characters. Is this OK?
-- Non-printable data causes checkpoint to fail. I think that this is a question that should be asked to Support and I will appreciate it if you update this thread with their answer.
- AlexKaras3 years agoChampion Level 3
Hi,
Thank you for the update!
> it will be fixed
Didn't they mention what the fix will be? Are they going to store all data, including non-printable characters, and compare considering these characters, or just skip non-printable characters, or something else?
Related Content
- 7 months agogdave
- 4 years agojodydowling
Recent Discussions
- 22 hours agojstaehlin