Business justification

We cannot do all the B2Qt environments our self but instead, we need to scale by enabling other parties in doing it. As part of this we need to provide documentation on how partners can test and verify using QTBUG-69748 Ability to create Qt commercial build and then QTBUG-68680 creating QBSP packages for delivery of their hardware support. Aim is that partners can add these in to their own CI and QA practices and have some guidance from us to verify if their self baked Qt can actually be called Qt.

Engineering effort

The test and verification ability by 3rd parties is split in to phases

1. Create documentation on how and what to test to verify self-made BSP with Qt (this User Story, separated from #3 below to allow fit in 5.12 time frame)
2. Create a test application that can be run on target device running through key Qt functions and give Pass-Fail verdict (QTBUG-70286)
3. Productize RTA framework with Squish for embedded testing so, that a board vendor can reuse that for Qt verification (QTBUG-69986)