ryannutt/unittest

Moodle question type for JUnit testing student code

unittest's Issues

Editor width on resize

The editor needs to resize to 100% width on window resize to keep it from either staying narrow or too wide.

Correct / incorrect needs to be based on quiz options

Instead of always showing the progress meter after an adaptive submission, it should be dependent on the quiz review options. Probably tied to the checkbox for whether correct and marks.

Method only submissions

Allow the entry of a single method only instead of having to shell the entire class. When the class is missing, the method would have to be wrapped in a class before compiling.

This would also take figuring out what the class name would be because the JUnit file will need the class name for tests to run.

Better JUnit formatting

Need to format the output from JUnit better. Maybe something like the table at codingbat.com. Take the actual JUnit output and wrap it in a hidden div that can be shown.

Attempts not always showing correct results

The results shown after an unsuccessful attempt are not always the correct result.

In some cases they are from a previous result on the same question. On some cases they're an attempt on other questions from the same quiz when there are multiple code questions.

They do appear to always be from the correct user though.

May be related to the reason that sometimes the percentage bar is showing correct when the actual attempt is not actually correct.

JUnit classname field redundant

The text field to enter the JUnit class name isn't needed. It should be able to be pulled from the file just like the student submitted class name is.

Data files

Add option to pull data files into the working directory so that code can be written to open and manipulate the data.

Hamcrest Jar not getting included in JUnit build classpath

Looks like only the JUnit.jar file is getting included in the classpath parameter when the JUnit test class is compiled which is causing issues with assertThat which comes from hamcrest.

Past submissions need to wrap in <pre> tags

The previous code submissions are showing as a single line. Ideally I could wrap the code in a pre and have it display correctly. But it looks like it might be stored in the database as a single line, which would have to be fixed first.

Fix policy file

Switched the policy file to be too often when testing file attachments. Need to lock it back down.

Check if java and javac exist prior to running

Need to add an error state if either java or javac, or the jar files, don't exist prior to trying to compile and run code. Right now it's just throwing a message that the JUnit couldn't run which isn't a good message.

show results on manual gradin

The compiler results need to show on the manual grading screen. Right now it doesn't show anything except points.

Make editor fullscreen

Use the fullscreen JS API to allow the editor to go full screen;

JUnit expected output in <>

Need to check formatting of how the JUnit output shows the expected and actual results. It's wrapped in <> which is causing it to disappear in the HTML.

Question results should wrap in pre tag

The results from the compiler need to be wrapped in a <pre> tag so the tabbing is correct.

Check that backup and restore work

Probably not, especially with the attachments that just got added in ticket #4;