We didn't get around to using @testable, which was introduced in Swift 2.x.
I just fixed that. This should dramatically speed up builds, and it also allows you to write a test that touches the internals of two modules (e.g., Storage and Sync). Source files no longer have to be members of two targets (e.g., Client and ClientTests) in order to test non-public APIs. I just landed #1440 (Bug 1239514) which switches master over to using @testable. Take a look at the PR if you want to see an example. I tested building and running tests with this, but it's possible I missed something. The rote fix is: * Make sure the source file isn't a member of a test target. * In the test, use `@testable import MyModule`. That's it. If you hit more difficulties, scream and find me, Nick, or Steph. Any files you've added in branches: please make sure they're not in two targets. Apologies for your bitrotting, but let it be known that I've got it way worse than you :)
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
