At the beginning of the week I broke out what was just HTTPTest in to 3 seperate classes for reuse and just to keep them nice and trim. Now all test cases are written in either HTTPTest or DAVTest, which all inherit at some point from TestObject^?.

Then I added some new tests and functionality that were DAV specific, and ported all the old test cases to use these new methods, it trimmed the lines of code in the scripts fairly significantly.

Then I broke out the test scripts into a setup function and a run function, which looks a lot more like test written to use the TestCase^? class in the upcoming framework. The inspiration for this was that I wanted to start running some stress and perf tests against cosmo, and for that I'll need to run reports and PUT test cases against the same account, since each test script assumes a fresh repository I had to break them up like this to get it to run.

There is now lots of fancy new features in TestObject^?, which I'll be leveraging for the upcoming framework. I also wrote stress.py, a stress testing script that runs multiple test objects in seperate threads for stress testing and outputs all the cummulative results.

I spent about 6 hours trying to get basic SSL python libraries working with no success. This was intended for a feature I wish to add to all the automation systems that can query bugzilla for a bug status if that bug is marked as having a currently logged bug. After this frustration I moved on to some cleanup work and other cosmo tasks so that I could at least get something tangible done for the day.

GENERAL STATUS

Cosmo automation is done for 0.3, in fact it's probably a little ahead. The last things I want to do that aren't required for 0.3 but I wish to do:

• We need to put in a hardware request and setup a performance rig (this will most likely be post 0.3 release)
• A day or two of general cleanup and stability, just because I don't know exactly when I'll be able to get back to cosmo automation or if it will even be myself who is doing it and I want to feel secure about what is there.
• Cosmo automation documentation - I'll probably do this after 0.3 release, I HAVE to start working on Chandler next week if we want to make the transition a smooth one so I'll probably put off the documenation a bit and weave it in to my other work for the next month.

All said and done cosmo automation is looking really good, it's very feature rich, lots of tests that are running stable and a little over 4 thousands lines of code (according to `cat *.py | wc -l`).