- identify the pain points of mobilefrontend in terms of difficulty, efficiency, and ease of building and maintaining features from their perspective
- brainstorm optimal solutions
- provide result to whomever {T156259} is assigned to
---
=Results=
##Pain points
* More than 1000 lines of JSON configuration with order of files and dependencies. Manually specifying and reasoning about the dependencies between files is error prone and has caused us many problems.
* Unit tests take too long to run since they require a running instance of mediawiki, so each test run needs to load a page and all the resources from the server. This complicates doing test driven development because of the long feedback cycles.
* Tooling runs through grunt, making it slower than it should.
* Example, running eslint directly from the cli, instead of using grunt, usually takes half or even a third of the time for doing the same linting.
* There are no code coverage reports, and when we had them we were at a quite low coverage.