Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-3036

Define different cache expiration times

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 3.6.1
    • Fix Version/s: 3.7.0
    • Component/s: Caching
    • Labels:
    • Testing Instructions:
      Hide

      This issue only needs to be tested in 1 device. The device should be able to use a 3G connection.

      1. Install the app in the device and login in a 3.7 site.
      2. Go to view your badges (More tab > Click your user > Badges).
      3. Perform a PTR in the list of badges to make sure the data is fetched now. Remember the time you did this, you will use it at the end of the test.
      4. Go to view your private files (More tab > Private files).
      5. Perform a PTR in the list of files to make sure the data is fetched now. Remember the time you did this, you will use it later.
      6. Go to the dashboard and check that you see the recent items block. If you don't see it, please add it using a browser.
      7. Perform a PTR in the dashboard to make sure the data is fetched now. Remember the time you did this.
      8. Now open any activity that isn't the one displayed as the most recent in the recent items block.
      9. Make sure you're connected to a WiFi network.
      10. After 5:30 minutes from the time of the step 7, restart the app. Check that the list of recent items hasn't been updated.
      11. After 7:30 minutes from the time of the step 7, restart the app. Check that the list of recent items has been updated. Remember the time you did this.
      12. Now open any activity that isn't the one displayed as the most recent in the recent items block.
      13. Disconnect from WiFi so you use a 3G connection.
      14. After 7:30 minutes from the time of the step 11, restart the app. Check that the list of recent items hasn't been updated.
      15. After 11 minutes from the time of the step 11, restart the app. Check that the list of recent items has been updated.
      16. Connect to WiFi again, login as teacher (if you weren't) and open the list of submissions in an assignment.
      17. Perform a PTR in the list of submissions to make sure the data is fetched now. Remember the time you did this.
      18. In web, login as a student that hasn't submitted the assignment and submit it now.
      19. After 15 minutes from the time of the step 17, open the list of submissions again. Check that the list of submissions hasn't been updated (the status of the user is still the old one).
      20. After 21 minutes from the time of the step 17, open the list of submissions again. Check that the list has been updated.
      21. In web with the same user as step 1, add a file to your private files.
      22. Login in the app with the user from step 1 and, after 55 minutes from the time of the step 5, open private files again. Check that the list of files hasn't been updated.
      23. After 1 hour and 1 minute from the time of the step 5, open private files again. Check that the list of files has been updated.
      24. In web as teacher/admin, award a new badge to the user on the app.
      25. After more than 1 hour from step 3, open badges again. Check that the list of badges hasn't been updated.
      Show
      This issue only needs to be tested in 1 device. The device should be able to use a 3G connection. Install the app in the device and login in a 3.7 site. Go to view your badges (More tab > Click your user > Badges). Perform a PTR in the list of badges to make sure the data is fetched now. Remember the time you did this, you will use it at the end of the test. Go to view your private files (More tab > Private files). Perform a PTR in the list of files to make sure the data is fetched now. Remember the time you did this, you will use it later. Go to the dashboard and check that you see the recent items block. If you don't see it, please add it using a browser. Perform a PTR in the dashboard to make sure the data is fetched now. Remember the time you did this. Now open any activity that isn't the one displayed as the most recent in the recent items block. Make sure you're connected to a WiFi network. After 5:30 minutes from the time of the step 7, restart the app. Check that the list of recent items hasn't been updated. After 7:30 minutes from the time of the step 7, restart the app. Check that the list of recent items has been updated. Remember the time you did this. Now open any activity that isn't the one displayed as the most recent in the recent items block. Disconnect from WiFi so you use a 3G connection. After 7:30 minutes from the time of the step 11, restart the app. Check that the list of recent items hasn't been updated. After 11 minutes from the time of the step 11, restart the app. Check that the list of recent items has been updated. Connect to WiFi again, login as teacher (if you weren't) and open the list of submissions in an assignment. Perform a PTR in the list of submissions to make sure the data is fetched now. Remember the time you did this. In web, login as a student that hasn't submitted the assignment and submit it now. After 15 minutes from the time of the step 17, open the list of submissions again. Check that the list of submissions hasn't been updated (the status of the user is still the old one). After 21 minutes from the time of the step 17, open the list of submissions again. Check that the list has been updated. In web with the same user as step 1, add a file to your private files. Login in the app with the user from step 1 and, after 55 minutes from the time of the step 5, open private files again. Check that the list of files hasn't been updated. After 1 hour and 1 minute from the time of the step 5, open private files again. Check that the list of files has been updated. In web as teacher/admin, award a new badge to the user on the app. After more than 1 hour from step 3, open badges again. Check that the list of badges hasn't been updated.
    • Affected Branches:
      MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_37_STABLE
    • Sprint:
      Moodle App 3.7.0

      Description

      Right now we always use 5 minutes as the cache expiration time. However, some requests are more likely to change than others so it'd be nice to have different expiration times, and use the right one in each WS call.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                7/Jun/19