Today and this week I have been going over the newest version of code posted by Phil. I have found a few bugs and have put them in the test cases file with have so that everyone can read it, I also told Phil and added these test cases to the technical documentation.
I also updated the technical document a little by adding a few more sections and pieces of information.

As for the user manual, I dont think anyone has made any changes to this since we submitted it last semester. These will be quite a few changes that need to be made to this because the way we originally plained the interface didn't work out as we expected. There are also section in this that need to be full filled. This will all be done once the program has a complete user interface and about 90% of the functionality has been implemented.

Todays and through the week mainly I have been trying to get the technical documentation up to date. This means adding in some test cases that are arising as people run the program and some other sections that need to be filled out.
There are still some sections that need major changes such as the section about the user interface. This section at the moment talks about the type of interface we were originally planning to implement, however this has changed. Once the interface is complete this section will then change.

As with trying to full fill the 10% of coding required from myself. I am trying to get my hands in there and change minor things or even help make the code easier to read and understand. At the moment I am not near this 10% contribution , however at this rate I plain on making it comfortably at the end of the project.

Yesterday and Today I just spent my time documenting what I have been doing recently. This meant filling out the Unit Testing section in the technical manual. The technical manual is slowly getting bigger which is good. At the moment it is just over 50 pages and as a group I would be happy if we could get it to almost 100 pages in length. This may be to much and may start to repeat itself but if we can fill it with a lot of information related to the processes and other ideas we have had throughout the development I think we could reach this mark quite comfortably.

Unit testing another attempt

After attempting to give unit testing another go and possibly even take parts of the code we already have and just testing those parts I am still unsuccessful. The other had told me that you couldn't unit test and I was trying to prove them wrong but in the end they were right. There are ways to Unit test C# code but once XNA is involved you simply can't do it.

A lot of books and websites all reference a program called NUnit which is a graphical or command line way to run the tests you create through the code within your class library. After trying and succeeding on the simple examples. I thought I could be able to manipulate this to work it with the code we have but it just isn't possible.

Here are some examples of the what I tried to achieve:

Here is a function within the CubicSpline class. I add this to a file then tried to do an assertion on it.
This all compiled and built successfully however when I tried to test it through the use of NUnit which uses test runners in the code to find which parts of the code are the tests

Above is the result I got from trying to run a simple assertion of the code above. I dont know if that error is readable but it says:

ClassLibrary1.TestLargest.TestGetCubicSpline:

System.IO.FileNotFoundException : Could not load file or assembly 'Microsoft.Xna.Framework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=6d5c3888ef60e27d' or one of its dependencies. The system cannot find the file specified.

Which simply means that this Unit testing will not work for XNA framework which is difficult when the our whole project is built using XNA framework

Testing Issues

After spending a good two days on  trying to work out possible ways to test what we have, reading many articles on the internet, watching videos , examples , googling a lot and reading the text book from the library testing looks like it is going to be a lot harder then originally thought. Due to the fact the the text book gives examples where you have to create a class library and write test code within this, you can't simply add a class library to a project that is already existing. Another example I saw on the internet looked like I could rework it to what we currently have but after spending a solid two to three hours and getting next to nowhere this idea was given up.

However there is still hope. The best option at the moment seems to be to take some parts of what we have and then write these up in a class library and write tests for them. These tests wouldn't impact any part of the program that we have but they would be there to make sure the finer and smaller parts of the program are working individually. Hopefully I will be able to do these within the next few days and at worst by the end of this week.

After todays meeting and discussion about unit testing I have been assigned the job to see if I can unit test the code. This task will not be easy but after reading and searching many articles on the web hopefully I can gain a grasp of this and give the unit testing a go.
I picked up a book from the universities library called "Pragmatic Unit Testing In C# with NUnit" . hopefully this will give me an insight into what I want to aim for and I can implement this in relation to our code. Hopefully I will be able to give this ago sometime tomorrow

Past few weeks

Over the break since my last post i continued to read and work on my C# skills so I can help contribute my 10% of code to the group and possibly even more.

Since we have gotten back and everyone has gotten up to speed. Jun was able to gain some proper user manuals from his work. I will use the manuals as a guide for the amount of depth and detail we should try and incorporate into our user manual. Although a lot of the information within these manuals is too much depth and also not needed for the level of program we are creating but these are still a good guide as what we should strive for our user and technical manual to look like.

Hopefully by the end of this week I will have updated both of our manuals and add new sections that will be filled out latter on as the semester continues.