Drop lowest displays incorrect points when you drop more points than you have

Description

Basically subject line says it alls.

The case this issue showed up in was with a Categories/Points gradebook. Set up a category with drop lowest higher than the number of effective items in the category. Then the points displayed will be incorrect.

For example if you have a gradebook with 7 items with a drop lowest set to 80. Initially you will get a proper #.

Now reduce the number of items by setting individual items to be not included in grade. The points will then become incorrect.

SP: 3

Attachments

2

Activity

Show:

Peter Peterson April 6, 2012 at 3:52 PM

QA PASS - works as described

Peter Peterson March 16, 2012 at 1:22 PM

So will this be an 1.8.0-a9 fix? If so lets change the Fix Version to reflect this.

Constance Fuller March 16, 2012 at 9:32 AM

Waiting for code review and qa

Jon Gorrono March 15, 2012 at 4:03 PM
Edited

Constance Fuller March 15, 2012 at 3:42 PM

Test cases:

Setup category with 3 items.

With drop lowest of 0 and all included, then category points are at 300.
Incrementally increased drop lowest to 4 drops. Category points decreased appropriately and was at 0 points for 3 and 4 drops.
Incrementally changed items to excluded. Category points value remained at 0 for each exclusion.
Leaving all items excluded, incrementally changed drops back to 0. Category points remained at 0.
Added new items until I had a total 8. Category points remained at 0 until the 8th item was removed. (3 excluded and 4 drops.) Category points ended at 100.
Changed that 8th item to be extra credit and category points went back down to 0.

Unit tests passed. Will check code into svn.

Fixed

Details

Assignee

Reporter

QA Status

PASS

Components

Fix versions

Affects versions

Priority

Created January 5, 2011 at 2:06 PM
Updated April 6, 2012 at 3:52 PM
Resolved March 16, 2012 at 9:32 AM