Goals

Stories

Measuring our speed improvements

"Speed of migration" will be rate of change of LOC of select source files (.jsp, *Action.java, *Controller.java, etc.) - comparing only jsp to jsp, ftl to ftl etc., over time (since we might expect, for instance, less LOC in ftl than jsp).

Measuring in this way will allow us to track a rough "burndown" of remaining UI code to convert (jsp and *Action.java LOC remaining).

Measuring testing effort

For testing related goals, we will measure:

  1. time spent modifying CreateSavingsAccountTest. 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: __________
  2. Number of issues (regressions) caught during CSS walk through. For previous FTL effort, number was zero since now walk through occurred. New Measurement: __________
  3. 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: ___________
  4. 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: _____________

More potential dev tasks

Spring Web flow examples in application

Frontend development aids

See also