Test coverage for src/components/app

[gregtatum]

In trying to find our worst offenders for test coverage, src/components/app/ stands out as being particularly bad. We might need to take on enzyme as a dependency and shallow rendering to properly deal with some of these components.

Files ordered by lines uncovered:

• [ ] Root.js (77 lines uncovered)
• [ ] ProfileSharing.js (67 lines uncovered)
• [ ] ProfileViewer.js (40 lines uncovered)
• [ ] UrlManager.js (32 lines uncovered)
• [ ] Home.js (27 lines uncovered)
• [ ] SymbolicationStatusOverlay.js (23 lines uncovered)
• [ ] TabBar.js (17 lines uncovered)
• [ ] ProfileFilterNavigator.js (9 lines uncovered)
• [ ] FooterLinks.js (3 lines uncovered)
• [ ] Initializing.js (2 lines uncovered)

┆Issue is synchronized with this Jira Task

[ria-19]

Can I work on this?

[julienw]

Since this bug was filed, this evolved quite a bit, I'd need to look at our current coverage.

Also if you are an outreachy student, please note that this project isn't part of outreachy this time.

If you're still interested, a good component to start with is FooterLinks. We don't use enzyme nowadays but react-testing-library, you'll find plenty of examples in our codebase.