Details
-
User Story
-
Resolution: Duplicate
-
P3: Somewhat important
-
None
-
None
Description
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 should package and productize the Qt test cases so that 2nd and 3rd party can verity Qt on the embedded environment (HW+BSP+OS) they have created them self. In other words, this is something we need to be able to scale and partner.
Implementation needs
Separate company confidential parts of RTA test setup from the non-confidential parts and then split the current RTA main repository into two, open and company confidential. Open up the non-confidential part in public repository. Re-structure DC RTA test sets so that those do not depend on special hw used in Qt Company RTA (SD-Muxes). In more generic works we need to generalize our DC RTA tests so that special parts are kept as optional extras. After all that is done we still need to document usage of this whole setup. All-in-all this is a really big task, multiple mm of work required.
Engineering effort
The test and verification ability by 3rd parties is split in to phases
- Create documentation on how and what to test to verify self-made BSP with Qt (
QTBUG-70661) - Create a test application that can be run on target device running through key Qt functions and give Pass-Fail verdict (QTBUG-70286)
- Productize RTA framework with Squish for embedded testing so, that a board vendor can reuse that for Qt verification (This User Story)
Attachments
Issue Links
- depends on
-
QTBUG-64512 Embedded RTA Perfection
- Closed
-
QTQAINFRA-1928 Open up RTA master repository
- Withdrawn
-
QTBUG-72433 Phase 1: Documentation on how to test and verify both a commercial Qt on Embedded BSP and corresponding QBSP
- Closed
- is replaced by
-
QTBUG-76302 Phase 1½: QBSP verification on Testrail with HW partners
- Blocked