Testing

Test Protocol

1. Does running unit tests cd /var/www/appstore ; /opt/miniconda/bin/python manage.py test work?

2. Does the front page load?

3. Does "All Apps" load?

   1. Does sorting work as expected?

4. Does a category load?

5. Does a 2.x plugin page load? (e.g. /apps/psicquicuniversalclient)

   1. Does plugin downloading work?
   2. Does "Search for posts" work?
   3. Does ratings work?

6. Does a 3.x app page load? (e.g. /apps/cluego)

   1. Do release downloads work?
   2. When a release is downloaded, is it reflected in the stats page?

7. Does app page editing work?

   1. Icon?
   2. Any link field?
   3. Details editing?
   4. Deleting a 3.0 release?
      1. Does the release still show in the download stats?
      2. Does the release no longer show in the app page?
      3. Does the release no longer show in the backend?
      4. Does depending on the deleted release fail?
      5. Does submitting a jar with the same name and version succeed?

8. Does search work?

9. Do app author pages work? (e.g. /apps/with_author/John%20"Scooter"%20Morris)

10. Does the "About" page load?

11. Does the "Contact Us" page load and work?

12. Does the /backend/all_apps page work?

    1. Does it refer accurately to icon and release URLs?

13. Do the admin pages load?

Testing table

Feel free to repurpose this shared spreadsheet to organizing testing of a new release: https://docs.google.com/spreadsheets/d/1sIKGWvh08GFDBIodUqMPlg_QpWzF8SrvBC2nh1Ea_Gk/edit#gid=0

App Submission Test Protocol

App submissions will test the manifest file, the email notification system and approval protocol. Use a recently submitted app as a test case, i.e., something submitted after that latest update of the dev site. Alternatively, generate a new test jar from an app dev project.