QA/Execution/Web Testing/SUMO/Tips and Pointers: Difference between revisions

← Older edit

QA/Execution/Web Testing/SUMO/Tips and Pointers (view source)

Revision as of 23:13, 24 February 2011

1,721 bytes added , 24 February 2011

→‎Litmus

Rbillings

Confirmed users

1,504

edits

@@ Line 1: / Line 1: @@
 ===Overview===
-This page has been created to aggregate details/pointers/info related to the SUMO website which will aid in testing and will help newbies quickly ramp up.
+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.
-===Log in credentials for Staging===
+===Server and login information===
-*login:support
+*Production (live) server URL: [http://support.mozilla.com/ http://support.mozilla.com/]
-*password:stage
+*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==
 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.
-** 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 Roles==
+==User account roles==
-SUMO has many user roles with varying privileges.Listed below are some of the user roles along with their privileges.
+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)
@@ Line 55: / Line 64: @@
   * Translate the website interface
-(Need to add info related to user roles-Administrator and Forum moderator)
+'''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==
@@ Line 62: / Line 83: @@
 ==Articles==
-Articles still in staging (needing approval) are prefixed with '*'
+* 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'