Create feature test for ios_app with static frameworks

This commit is contained in:
Oliver Atkinson 2019-02-21 15:40:27 +00:00
parent 1599e8d173
commit 8de3712a44
2 changed files with 33 additions and 0 deletions

View File

@ -41,3 +41,15 @@ Feature: Generate a new project using Tuist
Then I should be able to test the scheme ATests
Then I should be able to build the scheme B
Then I should be able to test the scheme BTests
Scenario: The project is an iOS application with frameworks and tests (ios_app_with_static_frameworks)
Given that tuist is available
And I have a working directory
Then I copy the fixture ios_app_with_static_frameworks into the working directory
Then tuist generates the project
Then I should be able to build the scheme App
Then I should be able to test the scheme AppTests
Then I should be able to build the scheme A
Then I should be able to test the scheme ATests
Then I should be able to build the scheme B
Then I should be able to test the scheme BTests

View File

@ -40,6 +40,27 @@ Contains a single file `Workspac.swift`, incorrectly named workspace manifest fi
This application provides a top level application with two static library dependencies. The first static library dependency has another static library dependency so that we are able to test how tuist handles the transitiveness of the static libraries in the linked frameworks of the main app.
```
Workspace:
- App:
- MainApp (iOS app)
- MainAppTests (iOS unit tests)
- A:
- A (static library iOS)
- ATests (iOS unit tests)
- B:
- B (static library iOS)
- BTests (iOS unit tests)
```
Dependencies:
- App -> A
- A -> B
## ios_app_with_static_libraries
Same as `ios_app_with_static_libraries` except using static frameworks instead of libraries.
```
Workspace:
- App: