Add E2E test for exposing public enums from ObjC to Swift #147
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part I of fixing #140 - E2E test that covers a scenario reported in the issue:
NS_ENUM
)-Swift.h
contains an absolute path to the Bridging header.-Swift.h
content in an artifact, the build may fail if a local machine has a different absolute SRCROOT than the producere2eTests/StandaloneSampleApp
This Standalone test is failing (as expected, the fix will be added in separate PRs) - for now, CI does not invoke it.
To run it locally, call
rake e2e:run_standalone
This PR contains 2 changes/fixes to the E2E tests:
valide_hit_rate