Testing Checklist

This testing checklist is primarily a reminder of what needs testing and reviewing each development cycle

1. Basic action set-up for each type
2. Advanced action set-up
3. Completing the action
4. Receipt of correct than you page and email
5. Each template view (as anon and auth )
6. Using forms and counters offsite
7. Portlet
8. Security
   • Are 'Action Records' viewable by an anonymous user?
   • Can data be downloaded by an anonymous user?
   • Are 'action definitions' listed in the search results?
9. Tracking system
   • Do all the cases in the [Tracking Testing]? pass?
10. Internationalisation (i18n) system
    • Can 'Action Elements' be translated using Linguplone and i18nLayer?
    • Can 'Action Editions' be translated using Linguplone and i18nLayer?
    • Are po files all loaded without errors on system start?
11. Translations
    • Are translations in po files complete for each language needed?
    • Do translations from po files get substituted on language switch (in web pages, emails and data downloads)?
    • Does full action switch language correctly for anonymous users?
12. Documentation
    • Has documentation been updated based on the changes made?
    • Has documentation been spell-checked and proof-read?
    • Has the documentation been exported into various formats for downloading?
    • Is the link to the documentation still working (and updated if it changes plus a re-direction page made)?
13. Add-ons: Data Merge