pygeo / easytest Goto Github PK

Set up travis.ci also for windows and python 3.x to check if module runs there as well.
Conda recipe would need to be updated accordingly.

2. The current file test checks for existence but it is also useful to assert for non-zero file size as I've come across this situation a few times using the RobotFramework.

Implement logging of failures in a LOG file
By how far can this be covered by nosetests already ???

For a full system I think we would need to add test suites, creating test reports/logging output of test suites. Alex, is this correctly understood? Is it also correct that all this functionality is covered by other classes in the general Python framework (TestSuite/TestResult/Test runners, etc..)?

Comment from Martin Evaldson

1. I've found that comparing checksums can be too precise for comparing output images generated via ESMValTool. When running the RobotFramework for testing I used the number of digits in the size of the file and this would actually change on occasion, e.g., from five digits to four. If running on the same machine, using the same software stack and the same modules loaded it might work but it is probably more convenient (for ESMVal, not for easytest in general) to have some leeway and instead look at the reference/test folder difference.

Implement general test routines tot compare graphical files (framework from Ben Little might be used here)