Internal testing draft plan below:

...

1. HDX Connect 
   a. (Login with your HDX org admin account) Upload a (temp) HDX connect dataset
   b. (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 (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 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. 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 in mailhog (one should be approved with attachment and the other should be declined). *if the test is not on production - check mailhog 
   f. Finally, delete the HDX connect dataset (you can leave it if not on production)
   
   +++ end of test +++
   
2. 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. 
   
   
3. Edit data flow (A. overwrite old resource with new B. change resource from external URL <> local resource)
4. Contact the contributor/group message (either to everyone, all admin, all editors)
   a. (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 Check in mailhogb. (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
5. New account registration + request to join + request a new organization
6. Data Check (A. validate a local file + remote resource on Tools + B. validate a hxl-tagged resource on HDX)
7. Quick Charts (A. test making quick charts on Tools + B. After testing 2(add data with hxlated data), turn on  
8. Make a dashboard/event page / Edit existing dashboard/event page
9. Add/Change carousel item on homepage
10. Add a new member from org page 'members' tab + login as admin to confirm the request&approve/decline the membership 
11. Send a question via "contact us" in FAQ page
    a. (without logging in) send a question *if the test is not on production - check question + check in 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 mailhogquestion + check in mailhog  

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

...

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.
   
   

...