Internal testing draft plan below:

...

A list of HDX features for periodic test:

*please testing to be done on feature- . Please check with yumi/dan which server is appropriate for test any of the feature below.

...

prior to testing to make sure feature- is in mirrored state as production. 

1. Add and edit data 
   1. Add a private dataset with 3 resources under HDX Org
   1. (Login as HDX org admin account) Go to "Add Data" and create a private dataset (alternatively access "Add data" from HDX org page under the logo)
   2. Upload 3 resources 
   3. Fill out the mandatory fields (red starred marked fields)
   4. Publish the private dataset
      
   5. Logout from your admin/editor account. Try to find the private dataset under HDX org (it should not be visible to non-HDX org member). Login as either HDX org member or admin and try to find the private dataset you created(it should be visible)
   2. Edit private dataset
   1. Go to the private dataset page you created and click on "Edit"
   2. Change details of a resource
   3. Add 2 more resources and delete one of the old resources
   4. Switch the privacy setting from "Private" to "Public" and fill out all mandatory fields
   5. Publish
   6. Check errors on dataset page
   3. Repeat a and b for public datasets
      
      
   4. HDX Connect
      1. (Login with your HDX org admin account)
   Upload
   1. 1. Go to "Add Data" and add a (temp) HDX connect dataset
   
   b.
   1. 1. . Fill out all required fields (*) and publish. 
      2.  (Logout from your HDX admin account) Find the HDX Connect dataset you created and(if you're not logged in - it should ask you to login. Login as HDX org editor or member) request access from "Data" view on main nav as well as from
   the
   1. 2. (HDX Connect) dataset page. Make 2 requests (1 you will approve, 2 you will decline as a maintainer).
         
   c. Check your email associated with HDX admin and make
   1. 1. Check in mailhog - make sure you received the 2 requests with messages you had entered. (if the test was not performed on production - these emails are caught in mailhog and actually not sent. so check the mailhog inbox + click on link to request page) 
   d.
   1. 1. Login again as a HDX admin + approve one of the requests (with attachment - use dummy xls or csv) and decline the other request. 
   e. Check your email
   1. 1. Check in mailhog (one should be approved with attachment and the other should be declined).
   *if the test is not on production - check mailhog 
   f.
   1. 1. Finally, delete the HDX connect dataset
   (you can leave it if not on production)
   +++ end of test +++
   Add data flow 
   a. (Login with your HDX org admin account) Upload several datasets (1. with a local file from your desktop 2. with remote resource - get it from existing dataset)
   b. 
   
2. Edit data flow (A. overwrite old resource with new B. change resource from external URL <> local resource)
3. Contact the contributor/group message (either
   1. 1. . Check on "Data" view on main nav to confirm it's deleted.  
4. Send "Contact the contributor" and "group message" (choose from: to everyone, all admin, all editors)
   a.
   1. (without logging in) Send a message to contributor from any dataset page. Do the same task while logged in (from any account) and make sure your email is pre-populated
   .*if the test is not on production - check mailhog New account registration + request to join + request a new organization
   1. . Check in mailhog
   2. (Login as HDX org admin) Send a group message from any HDX dataset page. You can pick from all/all admins/all editors. Check in mailhog
   1. Send a question via "contact us" in FAQ page
      1. (without logging in) send a question from FAQ page + check in mailhog 
      2. (while logged in to one of the account - admin/editor/member - check that your email is pre-populated in the form) send a question + check in mailhog and check the email address of the sender.   
         
   2. New user registration  
      1. New signup 
         1. Sign up as a new user using a new email address
         2. Make sure you receive email to "verify your email address" 
         3. Click on the URL in the email to complete the registration (create user name, password, fill out your name etc)
         4. Follow different subjects - location, topic etc
         5. Request membership to request to join the existing organization or request to create a new organization 
         6. Check the membership request email in mailhog 
         7. Logout and Login again(using account you just created) - check that you're directed to Dashboard when you login 
      2. Approve new member as org admin
         1. (Login as HDX admin) Go to HDX org page > "Members" tab. (or if you're continuing test from a - you can access the member's tab from the email link in step vi)
         2. "Approve" the request and assign a role (admin/editor/member)
      3. 
         
   3. Org admin tasks 
      1. Membership management - Invite a new user to join org
         1. (Login as HDX admin) Go to HDX org page. 
         2. Invite/add a new member from the 'members' tab. If the invited user is already signed up on HDX, the full name should appear as a dropdown option(by either entering the email address or full name) + should be immediately added as a chosen role(please refresh the page to check).
            If the invited user doesn't have account on HDX - she/he should receive an email to change password.
         3. Check in mailhog for 2 emails, 1 addressed to all members of the org that someone is added, 2 to the invited user to inform their account was created and need to update the password. 
      2. Membership management - delete a member in the organization
      3. Membership management - assign different role to a member in the organization
      4. Data maintainer - 
   4. Sysadmin tasks
      1. Make a dashboard /event page + edit existing dashboard/event page
      2. Add/Change carousel item on homepage
         1. Go to https://feature-data.humdata.org/ckan-admin/carousel/show (this URL may change in the coming weeks due to changes in security for sysadmin)
         2. Add a carousel item > publish > check on homepage for changes
         3. Delete a carousel item > publish > check on homepage 
         4. Edit a carousel item > publish > check on homepage 
            
            
      3. HDX Connect dashboard (only sysadmin can see)
   5. Data Check (A. validate a local file + remote resource on Tools + B. validate a hxl-tagged resource on HDX)
   6. Quick Charts (A. test making quick charts on Tools + B. After testing 2(add data with hxlated data), turn on  
   7. Make a dashboard/event page / Edit existing dashboard/event page
   8. Add/Change carousel item on homepage
   9. Add a new member from org page 'members' tab + login as admin to confirm the request&approve/decline the membership 
   10. Send a question via "contact us" in FAQ page
       a. (without logging in) send a question *if the test is not on production - check mailhog 
       b. (while logged in to one of the account - admin/editor/member - your email should be pre-populated in the form) send a question *if the test is not on production - check mailhog 

   Note: if you experienced any bug/issue, make a Jira ticket and tag Yumi/Dan.

   6

   Week of / Features tested	1	2	3	4	5	Add and edit data	Send "Contact the contributor" and "group message	Send a question via "contact us" in FAQ page	New user registration	Membership management	Sysadmin tasks	7	8	9	10	11	12
   (example) Week of 1/1/2019	x (no issue)	x (Jira link)	x (no issue)
   Week of 6/10/2019

   ...

   HDX runs on the open-source CKAN platform, and we are upgrading our version from 2.3 to 2.63 and adding a new feature, requestable datasets. As of today, the new version is ready on the feature server.

   We’d like your support in testing this upgraded version on the feature server. The main goal is to confirm that the new version behaves the same way as the old one, and to identify any issues or problems.

   ...

   A full list of testing scenarios is below. Feel free to choose any of them.

   **Be sure to test on the feature server, not on the actual HDX site.Please use this template to record any issue you experience.**

   ...

   All testing to be done at this url: https://feature-data.humdata.org

   User registration

   1. Sign up as a new user

   2. Request membership to a testing organization

   3. Check user dashboard

   4. Change your password and account details

   5. Check members page

   6. Check your role inside organization

   7. Contact the other members from organization by sending a group message

   8. Submit the Contact contributor form

   ...

   If the data uses the HXL standard, then HDX can automatically create customizable graphs and key figures to help you highlight the most important aspects of your dataset. This is called a "HXL Preview." For a HXL Preview to be generated, your dataset needs:

   ...

   Python HDX Library [for Python programmers]

   1. Test the HDX Ckan with the new site, trying as many different API calls and edge cases as you can think of.

   ...

   Map Explorer [desktop full page version]

   1. Url: https://test-data.hdx.rwlabs.org/mpx/#/

   2. Same actions as in above.
      
      

   ...