Set TEST_HOST and BUNDLE_LOADER for app unit tests

[ollieatkinson]

set TEST_HOST and BUNDLE_LOADER for Unit tests bundle for an app target so that the default generated test target runs

Resolves #204

Short description 📝

The default generated project did not set these two build configurations which meant that the app unit test target was not able to resolve the symbols stores inside of the application.

Solution 📦

By setting TEST_HOST and BUNDLE_LOADER ld is able to link the symbols and run the unit tests.

The implementation will look at the dependencies for the test target and the find the app to set as the test host. Currently this selects the first app, but we can expand on this in the future as and when we better understand peoples requirements.

Test Plan 👩‍💻👨‍💻

• Enable all unit tests for applications inside of fixtures
• bundle exec rake features
• swift test

[codecov]

Codecov Report

Merging #300 into master will decrease coverage by 0.02%.
The diff coverage is 96.8%.

@@            Coverage Diff             @@
##           master     #300      +/-   ##
==========================================
- Coverage   89.25%   89.22%   -0.03%     
==========================================
  Files         279      276       -3     
  Lines       10619    10501     -118     
==========================================
- Hits         9478     9370     -108     
+ Misses       1141     1131      -10

Impacted Files	Coverage Δ
...uistKitTests/Generator/SchemesGeneratorTests.swift	100% <ø> (ø)	⬆️
...Generator/TestData/GeneratedProject+TestData.swift	0% <0%> (ø)	⬆️
...TuistKitTests/Generator/ConfigGeneratorTests.swift	98.93% <100%> (+0.47%)	⬆️
Sources/TuistKit/Generator/ConfigGenerator.swift	98.14% <100%> (+0.14%)	⬆️
Sources/TuistKit/Generator/GeneratedProject.swift	100% <100%> (ø)	⬆️
Sources/TuistKit/Generator/TargetGenerator.swift	100% <100%> (ø)	⬆️
Sources/TuistKit/Generator/ProjectGenerator.swift	98.91% <92.85%> (-1.09%)	⬇️
...uistKitTests/Generator/ProjectGeneratorTests.swift	98.61% <97.43%> (-1.39%)	⬇️
Sources/TuistKit/Utils/InfoPlistProvisioner.swift	100% <0%> (ø)	⬆️
Sources/TuistKit/Models/Platform.swift	100% <0%> (ø)	⬆️
... and 7 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c910164...dc6d989. Read the comment docs.

[tuistbot]

	1 Warning
⚠️	Have you introduced any user-facing changes? If so, please take some time to update the documentation. Keeping the documentation up to date makes it easier for users to learn how to use Tuist.

Generated by 🚫 Danger

[kwridan]

Nice to see this being finally resolved! 👍

Sadly UI tests targets won't work with this :/

Target(name: "AppUITests",
                                 platform: .iOS,
                                 product: .uiTests,
                                 bundleId: "io.tuist.AppUITests",
                                 infoPlist: "Tests.plist",
                                 sources: "UITests/**",
                                 dependencies: [
                                     .target(name: "App"),
                                 ])

[ollieatkinson]

Thanks @kwridan - I've fixed the issue here: 43e1ab5

I set TEST_TARGET_NAME and ensured that the test target identity was being set at the top level PBXProject. I also added the ui tests to the ios_app_with_tests fixture.

I've rebased the work against master to test against the latest changes.

[kwridan]

nice work 👍 - both unit and ui tests now work!

We can revisit this and consider the enum solution suggested on the original issue (option 3 in #204) once we find more use cases for product specific attributes.