P3 SPARQ OS analyzed by Profilence QA Suite

  • In the first half of the video, the QA suite is modeling driver behavior by issuing UI events to SPARQ OS and collecting data from the system (this part of the video has been time-accelerated).
  • In the second half of the video, QA results are examined in the dashboard.
  • Maps application leaked resources and crashed every few hours.
  • The entire system UI crashed due to problems with the Map application.
  • Crashes in different parts of the Bluetooth subsystem.
  • When QA runs are performed systematically for each software release, product managers get a 360 view into software quality trends and most pressing issues. Estimating market-readiness and end-user satisfaction becomes easier.
  • With the comprehensive technical data collected during QA runs, engineering teams can start fixing the issues immediately, as there is no need to reproduce them. The time from issue discovery to fixing is greatly reduced.
  • QA runs are done in laboratory conditions, and data is immediately available for analysis. Instead of waiting for field trial results that take weeks to arrive and are often incomplete, issues can be discovered and fixed in days.
  • QA scope extends beyond the infotainment system and covers ECUs and other interconnected subsystems.