ScriptT3D: Testing in Progress ... errr ... DONE!

Update:
We interrupt the old blog content to bring you breaking news.

MIT Version of ScriptT3D Released!!!

ScriptT3D Resource
Yeah, I am done with the rewrite. The code is cleaned up, tested, and ready for more eyes. I think this is definitely the most solid release of ScriptT3D to date. Try it out, give me comments so I can cry into some tissues, and then I will fix the bugs or explain the "features".

Previous Blog Content:
Seriously, I must be a glutton for brain damage. I am in the process of learning to test the ScriptT3D interface to T3D. So I have delved into Unit Testing. The strange thing is that I kind of think it is fun. Part of the fun is the frame work was written by someone else. Python comes with a Unit Testing module called unittest. So it makes it a nobrainer to setup test fixtures and execute them. It is also something I have never done before so that makes it slightly more exciting than brushing your teeth.

The main driver for using unit testing is to reduce time spent finding out if changes I make introduced a bug. The interface I have created is somewhat complex. It would be easy to make a small change that is not noticeable readily. Another reason is I really should know how to unit test my code. As a professional coder I am often building interfaces for things and often waste time tracking down simple issues. Having some more tools to find issues with my code is a good thing. So I am getting pretty far along in testing my interface. I have a testing fixture setup so I can just add tests as determine parts that need testing. This all means that the code will be much more robust and maintainable in the future.

Here is a quick example of the unit test code:

# define unit tests
class SimObjectTests(unittest.TestCase):
    # setup for each test
    def setUp(self):
        # create a new SimObject for each test
        self.simobject = engine.evaluate('return new SimObject(TestSimObject);')
    # cleanup for each test
    def tearDown(self):
        # delete SimObject after each test
        engine.evaluate('{0}.delete();'.format(self.simobject))

    # tests
    def test_SimObjectsAccessByID(self):
        obj = SimObjects[self.simobject]
        objId = obj.getId()
        self.assertEqual(self.simobject, objId)
        #self.assertTrue(self.simobject == objId)

    def test_SimObjectsAccessByName(self):
        obj = SimObjects.TestSimObject
        objId = obj.getId()
        self.assertEqual(self.simobject, objId)
        #self.assertTrue(self.simobject == objId)

    def test_SimObjectsAttribException(self):
        with self.assertRaises(AttributeError):
            obj = SimObjects.badObject

    def test_SimObjectsKeyException(self):
        with self.assertRaises(KeyError):
            obj = SimObjects["badObject"]
        obj = SimObjects.TestSimObject
        objId = obj.getId()
        with self.assertRaises(KeyError):
            obj = SimObjects[int(objId)+100]

Here is the result of running this suite of tests:

Starting Unit Tests
test_SimObjectsAccessByID (__main__.SimObjectTests) ... ok
test_SimObjectsAccessByName (__main__.SimObjectTests) ... ok
test_SimObjectsAttribException (__main__.SimObjectTests) ... ok
test_SimObjectsKeyException (__main__.SimObjectTests) ... ok

----------------------------------------------------------------------
Ran 4 tests in 0.021s

OK
Finished Unit Tests