In this case the an incomplete latex setup on travis lead to missing tests in nbconvert, which prevented the tests from registering a bug. See jupyter/nbconvert#356 for the story...
IMO a testsuite should not skip any tests in a CI environment, so it would be nice if the decorator could raise a failure instead of skipping if it is run on a CI service (=change the default to fail if the command is not present on travis/appveyor/circleci).
CI like travis set some environment variables, so a simple test for such env variables could be used to change a skip to a fail.
In this case the an incomplete latex setup on travis lead to missing tests in nbconvert, which prevented the tests from registering a bug. See jupyter/nbconvert#356 for the story...
IMO a testsuite should not skip any tests in a CI environment, so it would be nice if the decorator could raise a failure instead of skipping if it is run on a CI service (=change the default to fail if the command is not present on travis/appveyor/circleci).
CI like travis set some environment variables, so a simple test for such env variables could be used to change a skip to a fail.