Internal testing draft plan below:
...
*testing to be done on feature- . Please check with yumi/dan prior to testing to make sure feature- is in mirrored state as production.
- HDX Connect 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 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. 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 in mailhog (one should be approved with attachment and the other should be declined).
f. 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. - Edit data flow (A. overwrite old resource with new B. change resource from external URL <> local resource)
- Contact the contributor/group message . Check on "Data" view on main nav to confirm its deleted.
- Add and edit data
Add a private dataset with 3 resources under HDX Org
(Login as either HDX org admin or editor account) Go to "Add Data" and create a private dataset (alternatively access "Add data" from HDX org page under the logo)
Upload 3 resources
Fill out the mandatory fields (red starred marked fields)
Publish the private dataset
- 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).
Edit private dataset
Go to the private dataset page you created and click on "Edit"
Change details of a resource
Add 2 more resources and delete one of the old resources
Switch the privacy setting from "Private" to "Public" and fill out all mandatory fields
Publish
Check errors on dataset page
Repeat 1 and 2 for public datasets
- Send "Contact the contributor" and "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. 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 - New account user registration + request to join an org + request a new organization
a. Sign up as a new user using a new email address
b. Make sure you receive email to "verify your email address"
c. Click on the URL in the email to complete the registration (create user name, password, fill out your name etc)
d. Follow different subjects - location, topic etc
e. Request membership to a testing organization OR request to join the existing organization
f. Check the membership request email in mailhog
c. Logout and Login again - check that you're directed to Dashboard when you login Tasks as org admin
a. Check members pageCheck your role inside organization
- Data Check (A. validate a local file + remote resource on Tools + B. validate a hxl-tagged resource on HDX)
- Quick Charts (A. test making quick charts on Tools + B. After testing 2(add data with hxlated data), turn on
- Make a dashboard/event page / Edit existing dashboard/event page
- Add/Change carousel item on homepage
- Add a new member from org page 'members' tab + login as admin to confirm the request&approve/decline the membership
- Send a question via "contact us" in FAQ page
a. (without logging in) send a question + check in mailhog
b. (while logged in to one of the account - admin/editor/member - check that your email should be is pre-populated in the form) send a question + check in mailhog and check the email address of the sender.
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
Sign up as a new user
Request membership to a testing organization
Check user dashboard
Change your password and account details
Check members page
Check your role inside organization
Contact the other members from organization by sending a group message
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]
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]
Same actions as in above.
...