QA/Execution/Web Testing/SUMO/Tips and Pointers
Contents
Overview
This page has been created to gather info related to QA of the SUMO website which will help you get started with testing the site.
Server and login information
- Production (live) server URL: http://support.mozilla.com/
- Staging (testing) server URL: http://support.allizom.org/
In-product-page redirects
- http://support-stage.mozilla.org/1/firefox/3.6a1pre/Darwin/en-US/firefox-f1
- http://support-stage.mozilla.org/1/firefox/3.6a1pre/Darwin/en-US/firefox-osxkey
Caching
SUMO (prod and staging) caches JS/CSS via Citrix NetScalers, memcached, and Smarty
- If you can't see a fix on staging, ask IT to check and see what its latest SVN revision # is.
- During a rollout to production, if you don't see fixes applied to production, it might be a stale git lock; ask IT to clear it (though this should be fixed by Reed's Nagios script)
SHOWFOR
User account roles
SUMO has many user account roles with varying privileges.Listed below are some of the user roles along with their privileges.
(Each group inherits permissions from the previous groups)
Anonymous
Anonymous users are people who are not logged in.
Anonymous users can: * View articles in the Knowledge base, Administration, How to contribute, and Live Chat documentation categories * Post to the Firefox forum * Submit article feedback. * Vote on article feedback polls
Contributor
Contributors are users that are logged in to the site.
Contributors can: * View articles in the staging area, and the testing area * Post to the Contributors forum and Off Topic forum * Edit or translating articles in the Knowledge base (pending review), Staging area, and Live Chat documentation
Reviewer/Approver
Approvers are community members deemed trustworthy enough to make direct edits to public documentation and review other contributor edits.
Approvers can: * Approve or reject knowledge base edits waiting for review * Rename articles * Edit or translate contributor documentation * View articles in the Archive * Create or edit dynamic content blocks
Locale Leader
Locale leaders are responsible for administration tasks for the site in a specific language. Locale leaders can:
* Edit or translate articles in the Administration category. * Translate the website interface
Forum Moderator
The Forum Moderators group is completely separate from Approvers and Local Leaders.
Forum Moderators can:
* Edit, move, delete, and lock forum posts
Administrator
The Administrator group has all the permissions of the previous groups and also has access to the website configuration controls. It is the Administrators job to look after the website as a whole.
Translation
The notation for interface translation that shows you can translate that string resembles a degree symbol.
Articles
- If you create a new article it will first reside in 'Staging Area'.
- New articles residing in staging area will not have an '*' prefixed to the article name
- An Approver approves an article in 'Staging Area' and moves it to 'KB'
- If you edit an article that is already in KB then a copy of that article is created in 'Staging Area' prefixed with *
- Once this article is approved then the approved article is moved to 'KB' and the article in staging exists with the new changes
Litmus
- To create a test suite for a project:
- Create a subgroup first with a name specific to the project [ex: Subgroup for SUMO 2.2]
- Create a test group that includes the new subgroup
- Create a testrun that includes the subgroup and testgroup
- TIP: when cloning a testgroup, the best options are 'preserve' or 'recursive' and not the default 'simple'