[TIMOB-26332] iOS/Android: Create executable native test project for native modules
GitHub Issue | n/a |
---|---|
Type | New Feature |
Priority | High |
Status | Open |
Resolution | Unresolved |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android, iOS |
Labels | n/a |
Reporter | Hans Knöchel |
Assignee | Unknown |
Created | 2018-08-23T10:25:19.000+0000 |
Updated | 2018-08-23T10:36:22.000+0000 |
Description
Right now, native module development is kind of stressful. We generate native projects that can be ran in Xcode (iOS) and Android Studio, but module developers still need to create a test project themself, build it once, go to the build directory and open the native project, link the module target to it, copy the app.js from the test project to it, swap the module from before with the dynamically generated one and finally hope that everything goes well. This developer experience is *horrible*; and it could be resolved quite easily. We only need to change our module project template to also include a test-target, which could be as simple as referencing the example/app.js by default.
For iOS, we could create a workspace that has a test project and the main module target.
For Android, I don't know how Android Studio links targets, but we could eventually create another target there as well, which can be ran from directly from Android Studio, similar to the "TitaniumTest" project to test the core-SDK.
No comments