Test Description 60k limit
Description
Environment
Test Plan
I feel like the test plan for this is
Create an assessment, have a description over 4000 characters (Use http://www.lipsum.com/ to generate)
See what happens when you put over 60000 in the description (should fail gracefully ideally)
Also test the comments field on feedback, this field also increased from 4000 to 60000.
Test this on MySQL and Oracle.
Attachments
is depended on by
is related to
relates to
Activity

Matthew Jones May 5, 2016 at 3:11 PM
Thanks David, created for this.
I don't know if anyone has tested the conversion scripts much yet. This is usually something we do right before we release. But better to catch it earlier.
David Bauer May 5, 2016 at 2:39 PM
I just noticed that the conversion scripts in this commit have the published assessment table listed as "SAM_PUBLISHED_ASSESSMENT_T".
I think the correct title should be "SAM_PUBLISHEDASSESSMENT_T"
https://github.com/sakaiproject/sakai/blob/11.x/samigo/samigo-hibernate/src/java/org/sakaiproject/tool/assessment/data/dao/assessment/PublishedAssessment.hbm.xml#L8

Matthew Jones April 19, 2016 at 3:49 PM
Marking tested based on Neals comments. I'll open a new ticket to capture question level correct/incorrect feedback not working still.
Neal Caidin April 15, 2016 at 3:57 PM
Testing on Mysql and Oracle nightly master , revision eb9e407a9de02cb8ac671a85ecc54904c8824eaa
I tested using a little over 10,000 characters in the Description/Intro and in the instructor comments back to the student. Worked in both of those cases.
Failed when trying with question level feedback correct/incorrect. Saving removes the question itself as well as the correct/incorrect feedback and throws a stack trace.

Bryan Holladay July 16, 2013 at 8:27 AM
attaching part2 patch for published settings page
Details
Details
Assignee

Reporter

Extend char limit from 4k to 60k in test description