[LHN Bugs] [Tracking] Audit and Stabilize Brick Road Logic in Left Hand Navigation #66716
Description
Coming from the post here
Proposal
Audit and Stabilize Brick Road Logic in Left Hand Navigation
Background
New Expensify is reaching a stable point where we double down on performance and reliability. We’re actively migrating our largest Collect customers, and preparing to onboard Control users.
Over the past few years, our rapid pace of feature development has led to some technical debt—especially around test coverage. One of New Expensify’s core features, the Brick Road (GBR/RBR)—our guiding path for users—has become unreliable. While we’ve been addressing bugs as they appear, the fixes often feel like a game of whack-a-mole: resolve one issue, and another pops up.
Problem
When users rely on the brick road to know where to focus their attention, if the brick road fails or falsely highlights reports requiring attention, then users lose trust in the core feature erodes - leading to frustration, reduced engagement, and potential churn
Solution
Let’s take a step back and address GBR issues holistically. This means auditing the entire feature from a product perspective, validating all key flows, and ensuring they’re backed by strong integration tests in both Auth and App. Specifically, we propose to:
- Define test cases that clearly outline how GBR should behave across key flows.
- Partner with a backend engineer to implement a robust suite of integration tests in Auth.
- Collaborate with a dedicated C+ to cover offline-first scenarios with automated tests in App.
- Work with Applause to reflect these flows in TestRail and remove duplicate tests.
- Document the testing philosophy in our App repository contributing guide, so community contributors can understand and extend GBR correctly.
By building this comprehensive test foundation, we’ll prevent future regressions and establish best practices for maintaining GBR logic in the Left Hand Navigation.
Metadata
Metadata
Assignees
Type
Projects
Status
Status