Currently we have some unit tests for UI, a lot of unit and integration tests for API, but rely mostly on ATH for feature and integration testing. 

This is perhaps not optimal, there must be ways where we can unit and even integration tests components without end to end testing with full browsers. Eg, could we aim for a pyramid of tests like: 

https://2.bp.blogspot.com/-YTzv_O4TnkA/VTgexlumP1I/AAAAAAAAAJ8/57-rnwyvP6g/s1600/image02.png from: https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html 

In scope: 

• Look at a way of reporting test coverage (so we can report on it) and know where we stand
• Consolidate test runners used (karma or mocha?) across modules
• Improve code coverage (even if small improvement) for unit testable areas in javascript code where it makes sense, using mocks, component testing, whatever
  • Add unit tests for Activity, Branches and Pagers tab to ensure that data doesn't "blink" when pressing "Show More" (see JENKINS-43702). Note: this is currently a bug on Pull Requests tab.