Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-938 SCORM player
  3. MOBILE-1351

New attempts are created when it shouldn't

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.8
    • Fix Version/s: 2.8
    • Component/s: SCORM add-on
    • Labels:
    • Testing Instructions:
      Hide
      1. Create a new SCORM (or delete all your attempts in an existing SCORM).
      2. Open it in the app (doesn't matter if it's in normal or preview mode).
      3. Go back to the entry page, do a PTR and check that now it shows that you have 1 attempt.
      4. Open the SCORM again, go back to the entry page and do a PTR again. Check that it still says you have 1 attempt.
      Show
      Create a new SCORM (or delete all your attempts in an existing SCORM). Open it in the app (doesn't matter if it's in normal or preview mode). Go back to the entry page, do a PTR and check that now it shows that you have 1 attempt. Open the SCORM again, go back to the entry page and do a PTR again. Check that it still says you have 1 attempt.
    • Affected Branches:
      MOODLE_28_STABLE
    • Fixed Branches:
      MOODLE_28_STABLE

      Description

      While testing the SCORM player we noticed that a new attempt is created everytime we open a SCORM. This happens if you start the first attempt in Mobile, since it uses attempt=0 when it should be attempt=1.

        Attachments

          Activity

            People

            Assignee:
            dpalou Dani Palou
            Reporter:
            dpalou Dani Palou
            Peer reviewer:
            Juan Leyva Juan Leyva
            Integrator:
            Juan Leyva Juan Leyva
            Tester:
            Juan Leyva Juan Leyva
            Participants:
            Component watchers:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Fix Release Date:
              22/Jan/16