Forum Discussion
Hi,
Are those  symbols added by TestComplete itself or by some other tool/editor?
Considering that table data are stored in an XML file it might be that these symbols break correct xml file structure and cause TestComplete to interpret data in an incorrect way.
Hi AlexKaras ,
Those  symbols are added by the TestComplete itself. Those symbols are there as I directly open the tc.Tbl files using Notepad++ after I saved the changes of the table in TestComplete. Same result if I'm using Notepad to open the tc.Tbl file.
- AlexKaras3 years agoChampion Level 3
> Those  symbols are added by the TestComplete itself.
Hm-m-m, interesting...
What if you delete them in Notepad++, save file (backup first! 😉 ) and try to open it in TestComplete. If table is opened fine in TestComplete (you will see expected table data) you may try to execute your test(s) to check if the problem appears again. Do you think this is something that is worth trying?
BTW, don't you (occasionally) have enabled setting to update table with actual data? In this case it might be that those symbols are present in the database data (but just are not displayed on screen), so TestComplete saves them into table and then fails to open the table because those data corrupt expected internal file structure.
- Josh_1473 years agoContributor
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.
- AlexKaras3 years agoChampion Level 3
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.
Related Content
Recent Discussions
- 7 hours agovladd1