Archive for October, 2012
– Nearly done with issue #847
– Work on issue #873
– Still waiting for an answer from aimenk and seanbud regarding issue #689 (user preferences). If I still don’t have an answer after closing the two issues above, I may have to start from scratch.
– Worked, Reviewed and submitted 856, finish off the issue released mark pull request 697 and 704.
– Currently working on fixing up issue 745 about fixing flexible marking scheme. However, the changed worked on by Daryn is quite messy and it may be easier to start from scratch.
– Doing manual testing to find issues.
– Continue looking for bugs to log
– Work on task related to integration testing.
– There is not enough hours in the day to do everything. We need 30 hours days and 10 days a week.
– Didn’t do much since the sprint.
– Sort of in the same boat, haven’t had much time since the sprint to work on anything but assignments which are due this week. I’m still working on a very simple bug that is generating a warning in the tests, but is being difficult to track down.
– There’s a few bugs I’m interested in tackling. Someone had mentioned that the functional tests are broken so I wouldn’t mind cleaning them up. Also, there’s a bug #475 about replacing some legacy js with
unobtrusive js. Many of the comments make me think this may have been completed but I could take a look and see what may have been missed.
– None at this point.
– Didn’t have time to look at the issue, tons of things due this week.
– My Flight back home got cancelled which pushed my schedule back by a day as well 🙁
– Solve issue #868, make my first pull request.
– Almost finished a bug about warnings, issue 271. Just need to update the code, merge and request a pull.
– Going to look through the bugs list and pick one. (if anyone’s got an easy/moderate one they can fling it my way)
– Midterm and interview next week will probably reduce my work on markus but my plan is to get stuff done this weekend and find some time hopefully
– Fixed issue 840 and made a pull request
– Need to revert unknown changes to “development.erb” as part of branch 840
– Learn more about Markus code base
– Find an issue to work on
-Nothing major post-sprint
-Find some bugs and fix them!
-Keep digging into Markus trying to get my head around what’s going on.
-Still catching up on other school work
I have created a table in the database for the test results. The
schema so far is as follows:
table “automated_tests” do |t|
The “pretest_result”, “build_result”, and “test_script_result” are just
long strings of xml that contain the output of the test runner. To be
honest I don’t have my head wrapped around how the test results are
going to be stored in the database, so I made this for a start to get
feedback early. Feel free to comment on this schema and I will make the changes.
I also have an example of an test result xml file that the test runner will generate. The XML looks like this:
<test> <assignment-id>2</assignment-id> <group-id>4</group-id> <pretest> <filename>c-style-checker</filename> <result> <status>pass</status> <marks-earned>4/4</marks-earned> <test-input>student-file.c</test-input> <expected-output></expected-output> <actual-output></actual-output> </result> </pretest> <build> <filename>gcc</filename> <result> <status>normal</status> <actual-output></actual-output> </result> </build> <test-script> <filename>test1.c</filename> <result> <status>fail</status> <marks-earned>2</marks-earned> <test-input>student-file.c</test-input> <expected-output>All tests pass!</expected-output> <actual-output>3 Failures</actual-output> </result> </test-script> <test-script> <filename>test2.c</filename> <result> <status>pass</status> <marks-earned>4</marks-earned> <test-input>student-file.c</test-input> <expected-output>All tests pass!</expected-output> <actual-output>All tests pass!</actual-output> </result> </test-script> </test>
Comment and let me know what you think of that too!
– Resque is installed to markus on my fork. Working with Brian on test launcher. Divided tasks between myself and Brian.
– Finish tasks assigned to me, hopefully before the wednesday meeting.
– None. I may need more to do as it turns out the test launcher isn’t a lot of work. I might talk to Derek about taking some of his work of his back since he seems to be assigned a lot.
– Working on Mina’s fork on the Test Launcher. Understanding how MarkUs can connect with the test server.
– Implement the Test Launcher so that it can gather information and send to the test server.
– Understand what needs to get done, haven’t had time to work on it since Monday.
– Fixing one of my old pull requests on the Assignment order bug I fixed. Updating the testing page to match the new specs.
– None. I plan on throwing a large chunk of time at this code on Wednesday to fix the old request as well to update the testing page to where it needs to be. Understanding how I send requests to the Test Manager is the next road block.
-Have a basic script that can be used to run a provided testing script and return the results as XML.
-Expand the script to include more languages and add support for testing scripts that must be compiled before execution (ie. C, C++, Java).
-Find a way to deal with timeouts and crashes that happen when testing student code
-None. I have an assignment due Friday morning, so I likely won’t get much work done until Friday afternoon.
Here are the punchlines from our group (students from Centrale Nantes):
- Played with MarkUs
- Organised meetings with different teachers of Centrale to get their opinion about MarkUs
- First version of the requirements of MarkUs ended
Next steps :
- Consolidation of the specifications of MarkUs
- Writing more precise scenarii
- Make a non formal poll to a sample of students of each year in Centrale
- Send our poll to students
Road block :
- MarkUs finally installed
- I played with MarkUs so as to understand it
- Meeting with Morgan Magnin and Simon Carolan
- We created a first version of the requirements document
Next steps :
- Write the scenarii for the Requirements document
- Meetings in group with Morgan Magnin and Simon Carolan
- First version of the Requirements document
- “Played” a bit with Markus
- Learn to use MarkUs
- Work on the Use Cases / Scenarii
- Work on reports of meetings with different teachers
- Review of Requirements Document
- Read MarkUs documentation
- Computer was down for 5 days but is now repaired
Next steps :
- Learn to use MarkUs
- Write Use Cases
- Brainstorm on the UI
- Meetings with Morgan Magnin, Vincent Tourre and Simon Carolan
- Work on meeting reports
- Creation of a first version of the requirements document
- Work on a preview of the last Requirements document
- Write reports for the project
- Played with MarkUs
- Work on the requirements document
- Redaction of the poll
- Meetings to understand the needs of teachers
- Go deeper into MarkUs
- Precise the requirements (use case, UI)
- Keep on meeting teachers
- Issues to use the corrector view