summaryrefslogtreecommitdiff
path: root/testapp/templates/exam/question.html
AgeCommit message (Collapse)Author
2013-07-03Merge branch 'fresh_java' of https://github.com/prathamesh920/online_test ↵prathamesh
into deploy_server Conflicts: testapp/templates/exam/question.html
2013-07-03corrected a small malfunctionHardik Ghaghada
2013-07-03clean codeprathamesh
2013-07-02Merge branch 'C-Cpp' of https://github.com/prathamesh920/online_test into ↵prathamesh
fresh_C_Cpp
2013-07-01edited JS to give a msg when the answer is correcthardythe1
2013-06-11Modified textarea in student interface to notify about using tabs for ↵Hardik Ghaghada
indentation
2013-06-10Added the snippet feature & cleaned JSHardik Ghaghada
2013-05-08Function to check C-C++ codeprathamesh
Added a function which compiles C and C++ code submitted by the student. 1) If compilation is successful, then the submitted code is tested using test-cases. 2) To test the function written by the student, a C++ file calls the function and passes the argument to the function. Then the function checks for the expected return value. 3) If the return value is as expected, then a different set of arguments are passed, and the output is checked. 4) If for all set of arguments the output is as expected then the student code is graded correct else the error is displayed to the student. Changed the way the code is graded. Previously, the algorithm checked the student code for all test-cases. If all the test-cases were satisfied, the last-line of the program was reached and printed "All Correct". So at any point if a test-case fails, the last line is not reached as the program was terminate. When the string "All Correct" was found in the output, the code was graded as RIGHT else WRONG. This is not a proper way for code checking, as the student code *may* contain a print statement with the string('All Correct'), and thus can get program RIGHT even though it is WRONG. So now the student code is tested as follows: 1) The code checks for all test-cases. 2) If all test-cases are satisfied then it returns 0. 3) If any one of the test-case fails, the program is terminated and will return 1. 4) Now depending on the return status(0 or 1), it will grade the code. a) if 0 then RIGHT b) if 1 then WRONG This ensures, no manipulation from student side.
2013-04-30Snippet feature implementedHardik Ghaghada
2013-04-29Added a separate textarea for non-editable code for snippet featureHardik Ghaghada
2013-04-26missed this file in the previous commitHardik Ghaghada
2013-04-26Dumped JS from HTML pages to separate JS filesHardik Ghaghada
2013-04-26Dumped all JS in question.js fileHardik Ghaghada
2013-03-18Added code snippets for questionsJay Parikh
2012-06-25implemented tabs & line numbers in textareaJay Parikh
2012-04-18changes for student interfacehardythe1
2012-03-28minor changeshardythe1
2012-03-22Autocomplete tagging functionalityhardythe1
2012-03-20minor UI changeshardythe1
2012-03-16changes to maintain the UI in various resolutionshardythe1
2012-03-15minor UI changesjayparikh111
2012-02-28changes to remove the inline css from every pagehardythe1
2012-02-24formating and identationhardythe1
2012-02-07changes in question.htmlhardythe1
2012-02-01Updated html file with new lookjayparikh111
2012-01-31Updated Question.html with new looksjayparikh111
2011-12-09Moved all the apps to testapp folderparth