- 19 Dec, 2016 1 commit
-
-
Albert St. Aubin committed
-
- 15 Dec, 2016 1 commit
-
-
Eric Fischer committed
-
- 06 Dec, 2016 1 commit
-
-
Previously, there was no way for ORA to check whether a given score was a staff score or not; we've leveraged the annotations stored with those scores to expose and use that data.
Eric Fischer committed
-
- 02 Dec, 2016 2 commits
-
-
This reverts commit 7cd8e282, which was accidentally pushed to master
Eric Fischer committed -
Eric Fischer committed
-
- 28 Sep, 2016 2 commits
-
-
Eric Fischer committed
-
Eric Fischer committed
-
- 27 Sep, 2016 2 commits
-
-
Eric Fischer committed
-
TNL-4696 When a staff override assessment is recorded, we now treat all the submitter's requirements as being fulfilled. This allows ORA tooling to match the progress page reported grade for the student by placing the AssessmentWorkflow into a DONE state. Acceptance tests have been updated, and are now also included in quality checks
Eric Fischer committed
-
- 16 Dec, 2015 16 commits
-
-
Able to enable full staff grading from studio, save without errors, and view the staff grading step as expected from LMS. Includes: -template additions, staff grading disabled by default -fetching real staff requirements -javascript to hook into the python backend -changing some default assumptions about assessment types -modifications to validation -small bugfix for scroll behaviorwith validation alert. -updates to existing unit tests -additional validation, serialization, and javascript tests -fix for staff requirements bug (no more duble-unpacking) -updates the bundled studio js file -moving StaffWorkflow initilization to api's on_init() method -acceptance tests (lms) -addition of "Staff Assessment Section" to test course for bokchoy tests -renaming `requirements` to `<type>_requirements` in assessment apis
Eric Fischer committed -
Previously, api.update_from_assessments() would call model. update_from_assessments(), then api._serialized_with_details(reqs), which would duplicate the update work we *just* did as part of getting the status. Now, update() and get_details() are totally seperate operations, and _serialized_with_details() is a read-only method that does not need to have requirements passed in. I've also standardized student_training and peer, the two assessment types that do *not* auto-complete on None requirements, to return False if None, and error out if passed {}. This is to allow staff_assess to pass None to indicate "Update thyself, if you don't depend on requirements" to the other step types. Also adding test_requirements_changed(), to confirm that workflows are updated when requirements change, even though thoe requirements are no longer explicitly passed to the getter.
Eric Fischer committed -
Fairly simple test, should help to provide some extra peace of mind.
Eric Fischer committed -
I misunderstood what was happening in my cursory investigation earlier - all that needs to change here is the type of exception being caught.
Eric Fischer committed -
TNL-3464
cahrens committed -
Staff assessments can now mark workflow as being done, with proper handling for blocking workflows (such as peer), to hide a score if the submitter has not yet fulfilled their obligations. Includes tests. Also contains a tiny bugfix for a previously unexecuted codepath.
Eric Fischer committed -
This test is trying to confirm behavior when an api cannot be loaded. It is no longer possible for an AssessmentWorkflow to have been created without going through __init__(), so the latter part of this test is now trying to confirm assumptions about an impossible state. I recommend we just remove it.
Eric Fischer committed -
Eric Fischer committed
-
Eric Fischer committed
-
TNL-3467
Andy Armstrong committed -
Andy Armstrong committed
-
Eric Fischer committed
-
Staff assessments can now mark workflow as being done, with proper handling for blocking workflows (such as peer), to hide a score if the submitter has not yet fulfilled their obligations. Includes tests.
Eric Fischer committed -
Previously, I moved some assumptions out of class contstants and into code, in `start_workflow()`. Turns out, it's also possible to load a model from the database, which bypasses this check and fails to fill out self.STATUS properly. Refactoring so that `include_staff_in_class()` gets called in both cases.
Eric Fischer committed -
Changes include: -modifies requirements to gt an updated version of edx-submissions -adds set_staff_score to the AssessmentWorkflow model, which will record a new annotated score using edx-submissions functionality -prevents recording non-staff scores if a staff score exists -modifies update_from_assessment to call set_staff_score as needed -this includes changes to both the workflow model and its api -modifies get_score to allow staff overrides as optional -modifies the assessment serializer to include id information -adds this information to get_score method in self, ai, peer, and staff apis, to expose c ontributing_assessments where needed -fixes a small bug regarding None vs {} in the peer api -adds staff-assessment to the xblock, and makes it always available -uses the new force_update_score parameter on the workflow api when recording a staff assessment
Eric Fischer committed -
TNL-1162
Usman Khalid committed
-
- 13 Nov, 2015 2 commits
-
-
muzaffaryousaf committed
-
TNL-2818
Usman Khalid committed
-
- 16 Sep, 2015 1 commit
-
-
Will Daly committed
-
- 02 Mar, 2015 1 commit
-
-
TNL-708
Usman Khalid committed
-
- 14 Jan, 2015 1 commit
-
-
TNL-900
muzaffaryousaf committed
-
- 28 Jul, 2014 1 commit
-
-
Point setup instructions to the README Add instructions for combining/minifying static assets Update workflow overview architecture docs Update AI grading architecture docs Use napoleon keyword argument instead of kwargs Fix example usage docstrings in AI API
Will Daly committed
-
- 11 Jun, 2014 2 commits
- 10 Jun, 2014 1 commit
-
-
Refactor workflow API to avoid hard-coding first step logic.
Will Daly committed
-
- 09 Jun, 2014 4 commits