Comment 4 for bug 1537063

I personally would like to keep some sort of integration rake tests that isn't NOOP for fuel-library because NOOP 1) takes forever and 2) does not actually run cleanly on my OSX machine (too many linux assumptions, not enough mocks). I think it would be acceptable to make the unit tests only check the changed modules (as done via fuellib_unit_tests) but I think it's also a good idea to run all of the modules in at least 1 job to check integration via rake rather than noop.