The iOS implementation of integration_test uses a C preprocessor macro to make it easier to avoid some boilerplate. This makes it impossible to reuse that code from Swift, or to set breakpoints.
Rather than defining and encouraging users to use INTEGRATION_TEST_IOS_RUNNER, we should just have users call the right method(s). This will also make it easier for users to write Swift based test files for this, should they so chose (right now the instructions are ObjC only).
The iOS implementation of integration_test uses a C preprocessor macro to make it easier to avoid some boilerplate. This makes it impossible to reuse that code from Swift, or to set breakpoints.
Rather than defining and encouraging users to use
INTEGRATION_TEST_IOS_RUNNER, we should just have users call the right method(s). This will also make it easier for users to write Swift based test files for this, should they so chose (right now the instructions are ObjC only).