         
     }
     
+    // still 3. in RFC. This is the first decision we make in
+    // api design with regards to headers. Currently if nothing
+    // is passed in to the `headers` parameter (as is the case)
+    // with the convenience initialiser. We assume that the csv
+    // contains headers. If the headers are passed in, then we
+    // assume that the csv file does not contain them and expect
+    // it to be parsed accordingly.
     func testThatItParsesRowsWithoutHeaders() {
         
         testString = withoutHeader

public let withNewLinesInQuotes = "Year,Make,Model,Description,Price\r\n1997,Ford,\"E350\",descrition,3000.00\r\n1999,Chevy,Venture,\"another, \"\"amazing\"\",\r\ndescription\r\n\",4900.00\r\n"

class CSwiftVTests: XCTestCase {
   // modelling from http://tools.ietf.org/html/rfc4180#section-2
    
    var testString: String!
    
    func testThatItParsesLinesSeperatedByNewLines() {
        testString = newLineSeparation


        
    }
    
    //3.  There maybe an optional header line appearing as the first line
    //of the file with the same format as normal record lines.  This
    //header will contain names corresponding to the fields in the file
    //and should contain the same number of fields as the records in
    //the rest of the file (the presence or absence of the header line
    //should be indicated via the optional "header" parameter of this
    //MIME type).  For example:
    
    //field_name,field_name,field_name CRLF
    //aaa,bbb,ccc CRLF
    //zzz,yyy,xxx CRLF
    func testThatItParsesHeadersCorrectly() {
        
        testString = newLineSeparationNoEnd
