Forum Discussion
10 Replies
- Colin_McCraeCommunity Hero
Are you creating the CSV using Excel?
I seem to recall Excel cell formatting affecting how values are read in by external sources such as TestComplete.
Try formatting the cells as text before saving the CSV. Adding the "a" and it coming out right does suggest that the added "a" causes the content to be treated as text so passed through correctly.
(Or try creating it in notepad instead)
- vijay_bhaskarOccasional Contributor
Tool is generating the CSV file, which is used as the input source for the Automation. I will be using those values as the input to the application which is read from CSV using DDT CSV Driver.
- Colin_McCraeCommunity Hero
What tool?
(You really need to give specific information if you want useful answers!)
And try manually creating a CSV yourself (using notepad) and feed it that and see what happens. At least then that will tell you if the problem is the formatting of the CSV by "the tool" (whatever it is) or TestComplete when it reads it in.
All my tests (scripted) are data driven using data read in from an Excel spreadsheet (I don't use the DDT object, I have my own IDE extension modules which effectively form a test framework). I just tried feeding a textbox 10.10.10.10 from my Excel input sheet and it worked perfectly. The Excel cell format is "General" but the 10.10.10.10 being preceeded by "P:" (part of my framework, the "P:" indicates a parameter. It's not part of the actual data it feeds the TextBox) would likely cause Excel to treat it as Text and so not try and apply any crazy number formatting to it (which it would without the "P:").
Related Content
Recent Discussions
- 2 days ago