how to test your contribution although nose and doctest are both used in code testingit is adviable that unit tests are put in tests doctest is incorporated only to make sure the code examples in documentation remain valid across different development releases on linux/unix systemsplease launch your tests like thismake on windowsplease issue this commandtest bat before you commit please runmake format so as to beautify your code otherwise your build may fail your unit test how to log pyexcel when developing source pluginsit becomes necessary to have log trace available it helps find out what goes wrong quickly the basic step would be to set up logging before pyexcel import statement import logging import logging config logging basicconfig(format='%(asctime) %(name) %(levelname) %(message) 'level=logging debugimport pyexcel and if you would use complex configurationyou can use the following code import logging import logging config logging config fileconfig('log conf'import pyexcel and then save the following content as log conf in your directory[loggerskeys=rootsourcesrenderers [handlerskeys=consolehandler [formatterskeys=custom [logger_root(continues on next page developer' guide