XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • 4.1.0
    • 4.0.2
    • Performance
    • Hide

      This issue only needs to be tested in 1 device.

      This issue should be tested by a developer, to inspect network requests and also modify cache times to make it easier to test (using the config override system in console). The names of the configs are: cache_update_frequency_usually, cache_update_frequency_often, cache_update_frequency_sometimes, cache_update_frequency_rarely.

      1. Open the app and login in a 4.0 site and go to My Courses. Check that the list of courses is successfully loaded.
      2. In web as admin, change the name of any of the courses the user can see.
      3. In the app, logout from the site.
      4. Change all cache times of the app to something low (e.g. 5 minutes). 
      5. Wait for that time to pass since you did step 1 and open the site and My Courses again. Check that the course list is loaded "fast" and it displays the old course name. A Refresh button should appear at the bottom eventually.
      6. Open the Network inspector and click the Refresh button. Check that the page is refreshed and now it displays the new course name. Check that no Network request (related to My Courses) was performed during this refresh.
      7. Repeat the steps 2&3&5. Instead of clicking Refresh, now open a new page (e.g. a course). Check that the Refresh button disappears when navigating.
      8. Go back to My Courses. Check that the page now displays the new course name (it refreshed automatically).
      9. Now repeat steps 2&3&5 but, right after opening My Courses, switch to another tab while the data is loading (you should do that before the Refresh button appears). Wait a few seconds and then go back to My Courses. Check that the page displays the new course name (it refreshed automatically).
      10. Now repeat steps 2&3&5 but, instead of changing a course name, change the course description. The Refresh button should not appear now because the change is not meaningful for the user in this page.
      Show
      This issue only needs to be tested in 1 device. This issue should be tested by a developer, to inspect network requests and also modify cache times to make it easier to test (using the config override system in console). The names of the configs are: cache_update_frequency_usually, cache_update_frequency_often, cache_update_frequency_sometimes, cache_update_frequency_rarely. Open the app and login in a 4.0 site and go to My Courses. Check that the list of courses is successfully loaded. In web as admin, change the name of any of the courses the user can see. In the app, logout from the site. Change all cache times of the app to something low (e.g. 5 minutes).  Wait for that time to pass since you did step 1 and open the site and My Courses again. Check that the course list is loaded "fast" and it displays the old course name. A Refresh button should appear at the bottom eventually. Open the Network inspector and click the Refresh button. Check that the page is refreshed and now it displays the new course name. Check that no Network request (related to My Courses) was performed during this refresh. Repeat the steps 2&3&5. Instead of clicking Refresh, now open a new page (e.g. a course). Check that the Refresh button disappears when navigating. Go back to My Courses. Check that the page now displays the new course name (it refreshed automatically). Now repeat steps 2&3&5 but, right after opening My Courses, switch to another tab while the data is loading (you should do that before the Refresh button appears). Wait a few seconds and then go back to My Courses. Check that the page displays the new course name (it refreshed automatically). Now repeat steps 2&3&5 but, instead of changing a course name, change the course description. The Refresh button should not appear now because the change is not meaningful for the user in this page.
    • MOODLE_400_STABLE
    • MOODLE_401_STABLE
    • Moodle App 4.1.0

    Description

      We should review the cache priority and find a more effective way to retrieve content from cache.

      We should evaluate whether we could start retrieving data directly from cache and do a WS request in the background, instead of doing WS requests and storing the data for cache.

      For example, when loading the list of courses we can retieve the data from cache, perform the WS request in the background and only if there are changes display a toast to the user: Tap to update

       

      Attachments

        1. mark all as read - notification screen.png
          79 kB
          Eduardo Manzanillo
        2. Screenshot 2022-08-23 at 07.39.40.png
          295 kB
          Dani Palou
        3. Screenshot 2022-08-23 at 07.40.17.png
          134 kB
          Dani Palou

        Issue Links

          Activity

            People

              dpalou Dani Palou
              jleyva Juan Leyva
              Noel De Martin Noel De Martin
              Pau Ferrer Pau Ferrer
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Clockify

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.