Okay, okay, I'll admit it: I'm an architecture astronaut. I'd join Architecture Astronauts Anonymous--but that'd be AAA, and we already use them for our car insurance. Anyway, here's my current trip into orbit:
If you click on that, you should see a page with a large textarea appear, in which a running log of tests begins. So far, all but two of the tests succeed for me in Safari, FireFox, and MSIE6. I've got a bit more work to do on writing tests, though, as well as working on the server side.
But, there are things going on behind the scenes in this test harness that I want to share right now before I fly off into space.
Testing with AJAX
First off, about a week ago, I mentioned an experiment in REST and XML with which I was starting to play. In a nutshell, it's a bastard hybrid between a wiki and an XML database, with a REST API. Well, at the time, I was just poking at it with invocations of cURL from the command line.
But, none of these quite fulfilled my requirements of a) being simple, b) working well with code continuity broken by asynchronous HTTP requests, and c) being learned by me in an impatient jiffy. So, I made this:
It's by no means general or even all that nice to look at, but I've got half a mind to further refactor this into my own AJAX-friendly mini-rendition of JUnit. To anyone out there: Let me know if this would be useful, or if I'm just wasting my time.
The closest I came was to
selenium-logging.js in the Selenium package, but that wasn't really what I wanted. So, I made this:
But wait, there's more...
I'll break off here and continue in another post with the server-side things I started doing with WSGI.