In order to run different test suites in cocoapods integration, you can create multiple .Podfile files as a "starting point" of the E2E test.
- File
{SUITE_NAME}.Podfilecontains a base Podfile that should be excercised - [Optional] File
{SUITE_NAME}.Podfile.configcontains a hash of extra xcremote-cache-plugin parameters that should be added to thexcremotecache()configuration in a podfile - [Optional] File
{SUITE_NAME}.Podfile.expectationsoverrides a set of default validation steps that should be checked after consumer's build. Supported steps are:hits,missesorhit_rate(e.g.100for 100$). By default, 100%hit_rateand 0missesare used - if you want to skip a validation step for a given suite, you can set it tonullin a dictionary