Confirmed users
1,504
edits
QA/Execution/Web Testing/SUMO/Tips and Pointers: Difference between revisions
QA/Execution/Web Testing/SUMO/Tips and Pointers (view source)
Revision as of 23:13, 24 February 2011
, 24 February 2011→Litmus
(→Litmus) |
|||
| (18 intermediate revisions by 5 users not shown) | |||
| Line 4: | Line 4: | ||
===Server and login information=== | ===Server and login information=== | ||
*Production (live) server URL: [http://support.mozilla.com/ http://support.mozilla.com/] | *Production (live) server URL: [http://support.mozilla.com/ http://support.mozilla.com/] | ||
*Staging (testing) server URL: [http://support | *Staging (testing) server URL: [http://support.allizom.org/ 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== | ==Caching== | ||
SUMO (prod and staging) caches JS/CSS via Citrix [http://citrix.com/English/ps2/products/product.asp?contentID=21679 NetScalers], [http://www.danga.com/memcached/ memcached], and [http://www.smarty.net/faq.php#5 Smarty] | SUMO (prod and staging) caches JS/CSS via Citrix [http://citrix.com/English/ps2/products/product.asp?contentID=21679 NetScalers], [http://www.danga.com/memcached/ memcached], and [http://www.smarty.net/faq.php#5 Smarty] | ||
* If you can't see a fix on staging, ask IT to check and see what its latest SVN revision # is. | * 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 [http://stackoverflow.com/questions/119444/locking-binary-files-using-git-version-control-system stale git lock]; ask IT to clear it | ** During a rollout to production, if you don't see fixes applied to production, it might be a [http://stackoverflow.com/questions/119444/locking-binary-files-using-git-version-control-system stale git lock]; ask IT to clear it (though this should be fixed by Reed's Nagios script) | ||
==SHOWFOR== | |||
[http://support.mozilla.com/en-US/kb/Using+SHOWFOR#Blocks_of_content_with_lists_and_different_version_numbers http://support.mozilla.com/en-US/kb/Using+SHOWFOR#Blocks_of_content_with_lists_and_different_version_numbers] | |||
==User account roles== | ==User account roles== | ||
| Line 57: | Line 64: | ||
* Translate the website interface | * 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== | ==Translation== | ||
| Line 64: | Line 83: | ||
==Articles== | ==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' | |||