Picture of Chris Gillison
PLEASE HELP! Course being set as complete when I fail the assessment
by Chris Gillison - Wednesday, 13 June 2018, 6:00 PM
 

Hi all,

I'm not aware I've done anything differently to the other courses I've developed using the framework but for some reason my latest course shows up as completed even if I fail the assessment (using Moodle). In my config.json I have the following:

"_spoor": {
        "_isEnabled": true,
        "_tracking": {
            "_requireCourseCompleted": true,
            "_requireAssessmentPassed": true,
            "_shouldSubmitScore": true,
            "_shouldStoreResponses": false,
            "_shouldRecordInteractions": true
        },
        "_reporting": {
            "_comment": "Your options here are 'completed', 'passed', 'failed', and 'incomplete'",
            "_onTrackingCriteriaMet": "completed",
            "_onAssessmentFailure": "incomplete",
            "_resetStatusOnLanguageChange": false
        }
    }

and in course.json I have this:

"_assessment": {
        "_postTotalScoreToLms": true,
        "_requireAssessmentPassed": true,
        "_isPercentageBased": true,
        "_scoreToPass": 80
    }

Is there anything else I need to do / could try? Slightly desperate as this is due for delivery tomorrow (Thursday) lunchtime! Please help!

Chris

Picture of Chris Gillison
Re: PLEASE HELP! Course being set as complete when I fail the assessment
by Chris Gillison - Wednesday, 13 June 2018, 8:02 PM
 

Panic over!

Created a new course for testing and noticed there is a new format to the spoor attributes namely:

"_completionCriteria": {
    "_requireContentCompleted": false,
    "_requireAssessmentCompleted": true
}

...taking completion criteria out of the "_tracking" attributes altogether! Adapt sure keeps a man on his toes.

 

Picture of Matt Leathes
Re: PLEASE HELP! Course being set as complete when I fail the assessment
by Matt Leathes - Thursday, 14 June 2018, 8:49 AM
 

Hi Chris

Possibly our fault - when we released v3.0.0 we forgot to update config.json to have those settings in right place; this was fixed fairly soon after in the master branch and then released as part of v3.1.0

We try to avoid making these sorts of changes if at all possible but in this case it was absolutely necessary to avoid the xAPI plugin (and anything similar) from having to duplicate those settings and code.