...
- document eclipse FTL configuration for hot FTL pages
- Proposal - One timeboxed story on FTL spike - MIFOS-4409 4409 (to be completed in MIFOS-45734573 )
- Measure speed of migration of another area of Mifos. Compare established baseline (12 or so data points of historical LOC counts from git) with these new measurements.
...
- speeding up ui conversion
- hot Freemarker and Java reloading enabled via Michael Vorburger's Workspace 2.0 (see also MIFOS-40994099 )
- unit tests of [spring] webflow
- new, reusable Freemarker macros/widgets, such as the "progress tracker"
- new, reusable datatables-based display of search results in create savings flow
- better css classes (TODO: provide example)
- improved ci configuration: faster feedback when builds fail
...
For testing related goals, we will measure on creating Center workflow:
- time spent modifying CreateSavingsAccountTestCreateCenterTest. For previous FTL efforts (ie: one "flow" (aka "wizard" or multi-step form), ensuring test verified all facets of page was not addressed. New Measurement: __________
- Number of issues (regressions) caught during CSS walk through. For previous FTL effort, number was zero since now walk through occurred. New Measurement: __________
- Number of layout or functional bugs logged during testing phase (missed during walk through). For previous FTL efforts, this was typically 5-10 issues. New Measurement: ___________
- Time spent by QA manually testing the feature, including logging issues and retesting bugs fixes. For previous FTL effort, similar sized FTL conversion would be approximately 20 hours. New Measurement: _____________
...
- Workspace 2.0
- Install Eclipse Freemarker editor: http://freemarker.sourceforge.net/editors.htm (get JBoss Tools).
- Install Firebug (troubleshoot CSS issues quickly and easily): http://getfirebug.com
See also
- UI TechnologiesTechnology Guides (and its children, especially How To Add a Flow To Mifos)
- Common Ftl Macros
- Spring Spike
- FreeMarker Developer Testing Checklist
- UI Development
- How to make new UI development take less developer time (brainstorm? or something we apparently did a while back)