Connectivity Shift-Left Dashboard

Shift Functional Test Ownership from QA to Dev · WiFi · Bluetooth · SmartHome · Vega & FOS
W18 · May 1, 2026
Overall
Automation
📋 Overall Summary

The Connectivity Shift-Left initiative is tracking to Stage 1 completion on the Vega pilot by May 15 with FOS targeted for May 30. Three quality gates are defined and operational: Gate A (a/m/d pre-VML, middleware P0+P1 at 100% automated), Gate B (Two sub gates — B1: CR-merge functional BAT via Loom/CRUX blocking with a 4-hr SLA, B2: non-blocking targeting <1 day), and Gate C (vendor FW regression on the BSP pipeline).

For the pilot we selected Kanto (Vega TV), Brioche (Vega EFD), and Seabright (FOS8). Kanto and Brioche setups are ready across all gates and technology with 12 functional setups (Each Gate has 1 setup per technology — WiFi, BT and SmartHome) deployed and 50-iteration stability runs completed at >95% setup stability (last week: 20k TCs executed, ~97% setup stability across WiFi/BT).

Seabright Stage 1 is at stability validation phase — Gate definitions are same as Vega except Gate A, test case identification and infra build completed for Gate B1 and currently blocked for other gates due to constrained device availability in India.

On the tooling side, VegaLoom E2E POC is complete on one BT package and CRUX rule rollout is in progress across 70+ Connectivity packages; We will be live for 70%+ of the packages by end of this week (Non-blocking). VegaLens ground-truth and config validation are done and working on test case mapping with team for next phase (currently test running on gates has static coverage now, Phase 2 dynamic when production-ready). Completed and shared the setup requirement for all future deployment with LMS team.

🔵 This Week's Highlights (Apr 22 – May 1)

  • Test setup stability continues at >95% across 12 functional setups
  • VegaLoom: 70+ packages targeted, 20 onboarded; targeting 70%+ live by EoW (non-blocking)
  • Working on identifying auto trigger for a/m/d on actual device instead of reference platform
  • Automation log post-processing: categorizes setup, script, config, and DUT issues (demo completed)
  • Setup requirement for all future deployment completed and shared with LMS team
  • 50-iteration stability runs completed across all gates

🟣 Next Steps (May 1–9)

  • Go OFB for shift left for Vega devices (Kanto and Brioche) — test execution as non-blocking for CRUX rule
  • Continue enabling Gate B1 for FOS, start test case execution of B1 via PreCI pipeline
  • Address Dev team feedback on VegaLoom improvements with Loom POC
  • Complete automation log post-processing integration and truth validation across setups
  • Target: 70%+ VegaLoom packages live (non-blocking)
  • Begin test case mapping with VegaLens team for Phase 2 dynamic coverage
📊 Key Performance Indicators
1,189
Total Test Cases
Across all gates
12
Functional Setups
1 per gate × tech
~97%
Setup Stability
Target: >95% ✓
20/70+
Packages Onboarded
VegaLoom
87.2%
Overall Pass Rate
20,150 executions
62.7%
Automation Coverage
+4.1% WoW
3
Quality Gates
A, B, C defined
OFB
Vega Status
Non-blocking CRUX
📋 Pilot Execution Status (Vega + FOS)
PhaseWork StreamVega StatusVega ETAFOS StatusFOS ETA
PlanningQuality Gate Definition✅ CompletedMar '26✅ CompletedMar '26
PlanningTest Case Identification✅ 1,189 test casesMar '26✅ CompletedApr 17
PlanningSetup Feasibility✅ ValidatedMar '26✅ CompletedApr 17
ExecutionInfrastructure Build✅ 12 setups, >95%Mar '26🟡 B1 complete; others blockedApr 24
ExecutionSetup Stabilization (10 iter)✅ CompletedMar '26🟡 Stability validationApr 30
ExecutionPipeline Integration (Loom)✅ CompletedApr 17Not StartedApr 30
ExecutionE2E POC (10 iterations)✅ CompletedApr 24Not StartedMay 15
ExecutionCRUX Rule (all Conn Packages)🟡 In ProgressApr 30
Dev DeployTraining & OnboardingNot StartedApr 30Not StartedMay 15
Dev DeployGradual RolloutNot StartedApr 30Not StartedMay 15
🧪 Vega: Per-Gate Test Execution (Live · DOTS API · May 7, 2026)

Data from DOTS pools. Pass Rate = Pass/(Pass+Fail). DUT Issues from BT Shift-Left Stability Quip.

GateTechnologyPast 7 DaysPast 30 DaysKey DUT Issues (JIRA)
TCsPassRateTCsPassRate
Gate A WiFi 1,00987086.2% 1,00987086.2%
BT 89551958.0% 1,37082260.0% CARNIVAL-459, CARNIVAL-458, ACE-131487, ACE-122168
Gate B WiFi (B1) 58656396.1% 81369986.0%
BT (B2) 3,0772,43679.2% 3,9372,92774.3% ACE-131786, ACE-132374, CONNQA-32751, CONNQA-33151
Gate C BT 63056689.8% 8,2627,46290.3% ACE-131786, ACE-132374, PROJVEGA-317842
TOTAL 6,1974,95479.9% 15,39112,78083.0%
Note: Setup Stability = (Pass + DUT Failures) / Total. Most failures are DUT issues (real bugs caught pre-merge). No runs in past 24h for WiFi Gate A pool.
📡 Vega: DOTS Pool, TMS, Dashboard Configuration, Run Time
AttributeGate AGate BGate C
WiFiBTWiFi (B1)WiFi (B2)BT (B2)BT
Pool Connectivity_WIFI_Gate_A Connectivity_BT_Gate_A Connectivity_WIFI_Gate_B1 CONNQA-WiFi-GateB2 Connectivity_BT_Gate_B2 Connectivity_BT_Gate_C
TMS WiFi Gate A TMS N/A WiFi Gate B1 TMS WiFi Gate B2 TMS BT Gate B2 TMS BT Gate C TMS
Device Onboarded Kanto, BriocheKanto, BriocheKanto, BriocheKanto, BriocheKanto, BriocheKanto, Brioche
Dashboard WiFi Gate A WiFi Gate B1 WiFi Gate B2
Run Time Kanto: 10 hrs, Brioche: 9 hrs Kanto: 5h 45m, Brioche: —
7d Pass Rate 86.2% 58.0% 96.1% 79.2% 89.8%

Source: Sub-Zero Test Cases wiki · DUT Issues: BT Shift-Left Stability Quip

🏗️ Gate Architecture
Shift-Left Gating and Workflow

Gate A

Pipeline: a/m/d (Pre-VML)
Coverage: Middleware (100% P0+P1 automated)
Constraint: Component pipeline trigger
Note: FOS gate definitions same as Vega except Gate A

Gate B1

Pipeline: CR Merge (Loom/CRUX)
Coverage: Functional BAT; static now, dynamic via VegaLens later
Constraint: 4-hr limit; blocks CR merge

Gate B2

Pipeline: Patch-triggered non-blocking
Coverage: All remaining unique stable functional (A2+B de-duped)
Constraint: <1 day with parallelization; results to dev

Gate C

Pipeline: BSP Pipeline
Coverage: FW Regression = B1 + B2 combined
Constraint: Vendor FW gate

Source: Connectivity Shift Left Strategy wiki

🔧 Tooling & Integration

Click any status cell to update. Changes are saved locally in browser (localStorage).

ToolPurposeStatusDetailsLast Updated
Loom (CRUX) / VegaLoom CR merge pipeline trigger for Gate B1 In Progress E2E POC complete on 1 BT package. 70%+ packages targeted live by EoW (non-blocking). CRUX rule rollout across 70+ Conn packages. May 1, 2026
VegaLens Dynamic impact-based test selection In Progress POC done. Ground truth & config validation completed. Working on test case mapping for Phase 2. Currently static coverage; Phase 2 dynamic when production-ready. May 1, 2026
ARAM Dashboard Org-wide shift-left readiness Completed Connectivity data validated. Pending: Automated Test Stability % from tool owner. Apr 17, 2026
Boomerang Per-gate execution dashboards Completed A1, A2, B live. C, D in progress. Apr 17, 2026
Smoke Test Setup sanctity before every run In Progress Design finalized. Validates DUT, AP, DLI, host, RasPi. Halts on P0 failure. Code merged. Apr 25, 2026
Log Post-Processing Auto-categorize failure types In Progress Categorizes setup, script, config, and DUT issues. Demo completed. Integration and truth validation in progress. May 1, 2026
🐛 Key DUT Issues Found (Shift-Left Value — Real Bugs Caught Pre-Merge)

These are real device bugs caught by automated gates before code reaches VML.

JIRATechImpactDescription
AZMAXIII-5451WiFiHighRegistration fails after reboot on non-secure HVT devices (~44 TCs)
PROJVEGA-377465WiFiHighMTK ap0 connectivity layer — HostAP blocked (22 TCs)
ACE-131786BTMediumBrioche EVT HW — A2DP pairing/concurrency (~14 TCs)
ACE-132374BTMediumBrioche HOGP pairing failures (~8 TCs)
CARNIVAL-459BTMediumA2DP streaming reboot/concurrency intermittent (~6 TCs)
PROJVEGA-382865WiFiMediumHard reboot issue on Kanto (Gate A2)
⚠️ Risks & Blockers
#Risk/BlockerSeverityOwnerMitigation/ETAStatus
1Device Availability: Brioche short by 4 devices in Sunnyvale. Seabright limited in India.HighLMS/InfraProcurement trackedIn Progress
2Gate C Trigger: MTK FW regression trigger in BSP pipeline not finalizedMediumDev TeamAddress after Loom readyPlanned
3SmartHome MTS: Blocked on KT for trigger mechanismMediumchenaravZigbee setup in progressIn Progress
4VegaLoom access: Team needs access for most connectivity packagesMediumgunuWorking with POCs for CRUX ruleIn Progress
📊 Functional P0-P1 Automation Status (by Component × Product)

Case IDs from TeMet 2025. Fields queried LIVE from TestRail (May 12, 2026). Filters: P0+P1, Functional (trail contains "functional"), Section trail exclusion.

TechnologyProductTotal TCsAutomatableAutomatable %AutomatedAutomated %CoverageRemaining
Wi-FiOverall (dedup)50532865%10120%
30.8%
227
↳ Wi-FiEFD38030179%9224%
30.6%
209
↳ Wi-FiFireTV44129767%9522%
32.0%
202
BTEFD33330592%12638%
41.3%
179
BTFireTV715780%4462%
77.2%
13
SmartHomeEFD/FTV36627776%11030%
39.7%
167
TOTAL1,27596776%38130%
39.4%
586
Method: Case IDs from TeMet 2025 execution data (Unique Test Cases sheet). Fields queried LIVE from TestRail (May 12, 2026).
Filters: P0 (priority_id=11) + P1 (priority_id=1) only · Functional (section trail contains "functional") · Exclude deleted/archived sections
Fields: custom_automatable=1 (Yes) · custom_automated=True
Wi-Fi: TeMet old IDs → mapped to suite 408234 via 2020_to_2025_id_mapping.json. Product split via custom_compatiblefordevicefamily + custom_device_affected fallback. Overall row = deduplicated unique count (used in grand total).
Note: Co-ex excluded from shift-left scope.
⛔ Excluded Features: Remote, BLE Audio, UGS, ZTS, OTA, FFS, Coex, Co-ex, Concurrency, Ginger, Alibaba, ASHA, AVLS, Aquila, Luma, Airplay, Radar, Ethernet, X-rey, Miracast, Roaming, A2A, OOBE, Eero, OTA12:18, WHA, Captive Portal, Metrics, Tethering, AP Selection — test cases with these keywords in section trail are not included in the above counts.
📂 Raw Data: Shift-Left Functional P0-P1 by Component (SharePoint Excel) — one sheet per Component × Product for POC assignment.
📈 Sprint-over-Sprint Progression

Tracking 3 metrics across sprints. Format: xx% (numerator/denominator). Sprint cadence: 2 weeks (Mon–Sun).

Wi-Fi (Overall)

100% 50% 0% S1 S2 50.3% 17.9% 9.0% NEW

BT - EFD

100% 50% 0% S1 S2 89.1% 48.1% 42.8%

BT - FireTV

100% 50% 0% S1 S2 49.0% 35.4% 17.3%

SmartHome - EFD/FTV

100% 50% 0% S1 S2 76.8% 32.6% 25.1%
Automatable / Total
Automated / Automatable
Automated / Total
TechnologyMetricSprint-1 (Apr 27–May 10)Sprint-2 (May 11–24)Δ
Wi-Fi Automated / Total9.0% (106/1174)NEW
Automatable / Total50.3% (591/1174)NEW
Automated / Automatable17.9% (106/591)NEW
↳ Wi-Fi EFD Automated / Total16.8% (104/618)NEW
Automatable / Total67.3% (416/618)NEW
Automated / Automatable25.0% (104/416)NEW
↳ Wi-Fi FireTV Automated / Total9.8% (100/1023)NEW
Automatable / Total52.0% (532/1023)NEW
Automated / Automatable18.8% (100/532)NEW
BT - EFD Automated / Total43.8% (176/402)42.8% (176/411)▼ -1.0%
Automatable / Total88.8% (357/402)89.1% (366/411)▲ +0.3%
Automated / Automatable49.3% (176/357)48.1% (176/366)▼ -1.2%
BT - FireTV Automated / Total17.3% (91/525)17.3% (91/525)— 0.0%
Automatable / Total49.0% (257/525)49.0% (257/525)— 0.0%
Automated / Automatable35.4% (91/257)35.4% (91/257)— 0.0%
SmartHome Automated / Total25.1% (120/479)25.1% (120/479)— 0.0%
Automatable / Total76.8% (368/479)76.8% (368/479)— 0.0%
Automated / Automatable32.6% (120/368)32.6% (120/368)— 0.0%
Note: BT-EFD coverage dropped because Total increased (+9 cases moved to functional) while Automated stayed the same. Data stored in sprint_history.json.
🔍 Test Case Level Breakdown
YET TO START PLANNED IN SPRINT CR CREATED CR MERGED TESTRAIL UPDATED CTP DEPLOYED PIPELINE DEPLOYED
#Case IDTitleTechnologySectionPriorityStatus

Total cases in scope: 1,818. Use filters to narrow view. Data from TestRail live query (May 5, 2026).