FreeMarker Developer Testing Checklist

Owned by Former user (Deleted)
Last updated: Jan 26, 2011 by Adam MonsenVersion comment
2 min read

Goals

The goal of this checklist is to help developers identify issues that need to be addressed with new FreeMarker replacement pages. We can lower overall cost by addressing these areas early in the development process, and ensuring subsequent pages inherit a higher quality.

Each newly developed Freemarker MUST pass these checklist items before committing.

General Guideline

The below are specific details. In general, the page should look EXACTLY the same as before, unless an improvement has been identified and agreed upon with the PM team.

General checks

Layout/Navigation

  • Left navigation bar has expected links?
  • Search field?
  • Search button?
  • Breadcrumb?
  • Correct tab order?
  • Spacing between pages is correct?
  • Back button does not require repost?

Validation

  • Blank mandatory field is flagged with same error message?
  • Chars in numeric field?
  • Invalid date?
  • Can cancel page after error? Errors appear in red font?

CRUD functions

  • Submit with blank mandatory field?
  • Submit blank optional field has same behavior?
  • Can create new entry?
  • Can edit existing entry?
  • Can delete when allowed on page?

Internationalization

  • Display page with IS locale.
  • Do all UI strings all appear with @@@stringhere^^^ ?
  • Can enter Arabic characters - "عربية"
  • Can enter Chinese characters - "有"
  • Can enter extended characters - "òèßñ"

Permissions

  • If permissions exist for this page, do the permissions still control access to page/links when enabled/disabled?

Acceptance Tests

  • Do existing acceptance tests still pass with new changes?
  • If no acceptance test exists, create new card to build a new acceptance test(s) for this area and coordinate with QA on completing new tests.

Specific considerations for center/group/client related pages

Specific checks for loan related pages

  • Loan Products with weekly, monthly
  • LSIM enabled
  • GLIM enabled

Specific checks for savings related pages

  • Savings - tba

An Example: Define Labels

Comments from 2 August 2010 about the Define Labels page on http://ci.mifos.org:8085/mifos/

Layout

  1. Admin/ Define Labels is background shade is too tall
  2. Search button should be right aligned with search field
  3. Labels and edit boxes are too crowded to the left margin - move toward middle

Validation

  1. Current 1.6 validates for empty field (although fields don't have mandatory "*" in UI). New version allows user to enter blank value for a label.
  2. Input seems consistent - allows alpha numeric, retains upper/lower case.