There is a problem removing one answer from a FIB question and regrading the assessment

Description

Hi

There is an issue related to the FIB questions. To reproduce that issue you need to set in advance the property 'samigo.editPubAssessment.restricted' to 'false'. Steps to reproduce:

1. Publish an assessment which has any FIB question with multiple answers. E.g.: "1{a} 2 {b} 3{c} 4{d}".

2. Any student takes the assessment, answers "1a 2b 3c 4d" (which is the correct answer) and submits the assessment.

3. Modify the published assessment by removing one answer from the FIB question. The FIB question's text after removing one answer is: "1{a} 3{c} 4{d}"

4. Regrade and republish the published assessment.

5. If you check the student's results, his answer is "1a 3b 4c" instead of "1a 3c 4d".

I've attached an image to clarify this. It happens in trunk (11-SNAPSHOT).

Regards,
Raúl

Attachments

3
  • 08 Feb 2015, 04:18 AM
  • 22 Oct 2014, 07:44 AM
  • 30 Apr 2014, 03:17 AM

relates to

Activity

Valerio Cerni Conde April 17, 2015 at 7:38 AM

Tested successfully on http://sakai-test.atica.um.es/
Rev.39016 - 04-17-2015 05:43 - Sakai 10-SNAPSHOT (Kernel 10-SNAPSHOT)

Hudson CI Server March 31, 2015 at 9:19 PM

SUCCESS: Integrated in sakai-10-java-1.7 #185 (See http://builds.sakaiproject.org:8080/job/sakai-10-java-1.7/185/)
merge 9041282 from master (ottenhoff@longsight.com: rev 318219)

Sam Ottenhoff March 31, 2015 at 1:53 PM

10.x r318219

Ramon Garcia Martinez March 2, 2015 at 2:51 AM

Tested on http://nightly2.sakaiproject.org/ - Trunk on MySql

Works fine!

Steve Swinsburg February 8, 2015 at 4:18 AM

Instead of an alert, which is more difficult to hook into the edit workflow and can introduce accessibility issues, I have added a warning message directly on the edit page for FIB questions so people can make an informed decision. Screenshot attached.
PR: https://github.com/sakaiproject/sakai/pull/150

Fixed

Details

Priority

Affects versions

Fix versions

Assignee

Reporter

Created April 30, 2014 at 3:16 AM
Updated April 17, 2018 at 8:25 AM
Resolved February 9, 2015 at 9:22 AM