Bitrise Deep Dive - Tamas Bazsonyi: Android Fan Out Builds
Parallel testing and test reporting
From a high level, the process will look like:
- Trigger X test workflows from a Primary workflow and wait for them to complete
- Gather the test results from all X fan out workflows via the Bitrise API
- Generate a single Test Report for all X test results using bash
- Even though we will touch on the purpose and business benefits of this particular configuration, having a technical background is recommended to get the most out of this session.
Trigger X test workflows from a Primary workflow and wait for them to complete
Gather the test results from all X fan out workflows via the Bitrise API
Generate a single Test Report for all X test results using bash
Even though we will touch on the purpose and business benefits of this particular configuration, having a technical background is recommended to get the most out of this session.
Automated testing can be a slow process, especially when working with a large number of test cases. This method aims to speed up testing and your builds.
If you don't have a technical background, but think your team or product could benefit from learning more about Bitrise, reach out to us here!
- A mobile developer with some experience with Bitrise, Jenkins or any of their cloud-based alternatives;
- A (mobile) DevOps engineer, a Software engineer in test or any other engineering role involved in supporting mobile development teams with automation and/or testing;
- In a leadership role responsible for mobile development teams (VP of Engineer, VP of App Development, etc);
- Curious and eager to learn about mobile development tooling
- Work in a mobile-first company, where speed and quality matter;
- Like robots and/or cats
:00 - 10:20 AM PDT - Speed up Android Builds and Fan Out :20 - 10:30 AM PDT - Q&A session
Privacy and related information: