CocoaPods brings the functionality in an own Rake task, which silently executes the integration specs and moves the outputs for each spec to the after directory, so that this state is defined as accepted state and will be used from then on as spec. Most of it could be made generically available to other projects by providing an own Rake task in the gem, which could be added to the Rakefile, so that's is easier to rebuild the acceptable spec state.
CocoaPods brings the functionality in an own Rake task, which silently executes the integration specs and moves the outputs for each spec to the after directory, so that this state is defined as accepted state and will be used from then on as spec. Most of it could be made generically available to other projects by providing an own Rake task in the gem, which could be added to the Rakefile, so that's is easier to rebuild the acceptable spec state.
/c @carlossless