# Borrower Flow: Doc Collection Epic Testing Spike

## TLDR: Conclusion

**What**: Let's just add a few more unit tests for now to begin building up a foundation of coverage. E2E tests can be done later down the line.
**How**: As usual, let's add tests as-we-go, not in an upfront batch of work.

---

## Questions
- **Does test coverage go to the /dashboard route or end earlier?**
- Yes. They are more "smoke tests" and only test successful loading of the page.
- **Keeping in mind the dashboard will be reworked in 2022, how much coverage do we need here (short-term, long-term)?**
- _Answer at bottom of doc._

### Borrower Flow

With the Doc Collection Epic, we're only making mild tweaks to the way that the flow works: document upload slides are being removed from the flow and moved to the dashboard.

Since removal of the slides is almost entirely a matter of REMOVING isolated chunks of non-dependent code, a significant regression is unlikely.

For this reason, adding test coverage for this part of **the borrower flow** would not be very helpful (other than for extra peace of mind and for future-proofing).

#### Conclusion: For now, let's not add any additional test coverage for this part of the flow. It's stable/proven, and changes to it will be minor. Any testing we add will also likely be short-lived.

### Dashboard

For this epic, the updates to the dashboard will also be comparably simple, if drastically visually different.

However, since we recently seem to be building some inertia toward the concept of incrementally shifting chunks of the borrower flow to exist as modules on the dashboard, building up a solid foundation of tests will be great for confidence as we build.