Data-driven unit testing - Problem with CSV encoding?

Question

Hi,

I have the following CSV file that is used in my data-driven unit test:

File;expected
Resources.resx;default
Resources.de.resx;de
AttachmentDetail.ascx.it.resx;it
SomeOtherFile.rm-CH.resx;rm-CH

"File" and "expected" are the header. But if I want to get the "File"-column in the code like

TestContext.DataRow["File"].ToString();

I get the error

System.ArgumentException: Column 'File' does not belong to table ..

When I add the CSV file to an existing test-case over the test-method properties, it seems as if the "File"-column has some strange signs before its name, much like an encoding problem. But if I open the CSV file with Notepad, Notepad++ or even TextMate (on Mac) I don't see any such signs and I'm not able to get rid of them.

Can someone give me a suggestion about this problem?

Answer 1

What encoding is the file being saved?

From what I know, UTF-8 saved in windows notepad puts up some strange symbols in front of the file to know exactly what encoding was used when it didn't find any symbols that are needed for UTF8 (assuming everything is just plain ascii)

Did you edit the file using Notepad++ and saved it? I would try doing that and compare the results.

Answer 2

If you edit the CSV file in the VS2008 you can set the way the CSV file will be saved:

"File\Advanced Save Options..."

In the "Encoding:" drop down the default will be UTF-8. Change it to "Wester European (DOS) - Codepage 850". Leave the Line endings selection alone.

Answer 3

0

down vote If you edit the CSV file in the VS2008 you can set the way the CSV file will be saved:

"File\Advanced Save Options..."

In the "Encoding:" drop down the default will be UTF-8. Change it to "Wester European (DOS) - Codepage 1252". Leave the Line endings selection alone.