Bug 331766 - Extend KML unit test coverage of tag writers
Review Request #116644 - Created March 6, 2014 and submitted
Extends the existing .kml unit tests in tests/data and also adds new ones to maximize the test coverage of tag writers. There is one mention: The test, tests/TestGeoDataWriter fails because of the file tests/data/Tour.kml and I have the following diff: http://paste.kde.org/pksuar839 . I cannot figure out at the moment why it jumps over this tag. Syntactically, my .kml file seems correct, so I think there is a problem in the code ? I will try to find what causes this and I will come back with an update if necessary.
To find the problem, split it into smaller problems: - does the flytomode tag handler extract the value correctly when a .kml file is read? - does the geodata flyto object correctly save the value? - do the tag handler and the tag writer work on the same geodata flyto object instance? - does the tag writer write a "smooth" flytomode value correctly? Use gdb or debug print messages for each step. Also enable Marble's debug output (mDebug, pass --debug-info to bin/marble, some tests enable it manually as well, see there).
Review request changed
Solved the problem. :)
Revision 2 (+444 -19)