Suitest CI best practices¶
Continuous integration is big key in software development and testing automation should also be included within this ecosystem. Generally we recommend to prepare two different builds of the application that you are testing. One build intended for production and the second build being identical but also including the Suitest instrumentation library. By using our Network API, you can upload the builds directly from your CI system to Suitest configurations (Settings).
Our instrumentation library for Android TV should not be included inside of the production build of the application. Therefore the best practice is to have two compiled versions of the application, a "debugCompile" build and "releaseCompile" Build. Follow the application instrumentation within Android TV section to set up two compiled versions.
Apple TV (tvOS)¶
Our instrumentation library is completely dormant until it detects our application SuitestDrive connect to the device and app. Therefore there are no issues including it into you App store build. However, you should be aware that this will increase your application's size by roughly 4 MB. For more information refer to before uploading to the app store section.
HTML Based - Website, HbbTV / Freeview Play, Tizen, Orsay, LG webOS¶
Our instrumentation library for HTML-based platforms should not be included inside of the production build of the application. Therefore rely on automated instrumentation in the case of Websites, HbbTV / Freeview Play and LG webOS apps or manually instrument by inserting a small script in to the development or testing build of the application.
Our instrumentation library cannot be included in the Roku production signed package.
As Suitest only supports Roku packages in
.zip format, you have the option to rely on
or manual instrument the app within your CI.
When choosing automated instrumentation you can have just one build and upload it via the Network API to our servers.
Xbox One Native¶
Our instrumentation library for Xbox One should not be included inside of the production build of the application. Therefore the best practice here is to have a dedicated build configuration. Detailed instructions are under the managing native app builds section.