Kurt Sansom

[doctest](https://github.com/onqtam/doctest) seems lightweight and fast enough I think it would be a good candidate. Another thought that is not strictly testing would be testing from the README. e.g. from python...

Found my logic mistakes in the reader and wrong indentation in the writer. It appears to be working for me now. Still need to add some tests.

adding simple tests, need to rethink the polys section. should I read the polys section and then separate them into triangles, quads, and polygons?

the current implementation merges triangles, quads, and polygons into polygons on write. The read process specifies the cell types into the same triangles, quads, and polygons. Currently meshio doesn't support...

I forgot to commit the test files. they made need a little tweaking as I simply used the vtu files and applied the extract surface mesh in paraview and exported...

@nschloe Would it make more sense to derive a new package that contains format extensions rather than include it in meshio? does anyone have any thoughts or feedback on this...

Thank you for the input. tests appear to be passing now. More tests might be good and/or making better binary files tests. Currently I have the reader generating a warning...

What are the codecov checks checking?

Apologies for taking so long to respond. [vtp_testfiles.tar.gz](https://github.com/nschloe/meshio/files/7444807/vtp_testfiles.tar.gz)

@nschloe any feedback on this?