jessenoller.com

With the much-appreciated help of Bran­don Barry (with whom I just hap­pen to work) — there’s been a needed update to the test­but­ler code base I couldn’t get to — some highlights:

• Cleaned up the CSS, moved to blue­print for the larger por­tion of the CSS and the start of jQuery usage for the javascript portions
• Tem­plates have been cleaned up/gotten a major facelift
• site-media has been cleaned up
• Deleted unused code I had in the prototype
• Mod­els cleaned up

Over­all, it’s look­ing much bet­ter. Yes, it’s in a production-use now, and I love mark­down syn­tax. You can see some screen shots here.

We ditched the roomba-picture, I need to find some­one handy with art­work to maybe make some cus­tom icons/pics for us (I really want a cartoony-robot-butler)

There’s a lot I’d like to do, obvi­ously — but first I have to get started on the results track­ers and the cor­re­spond­ing nose plu­gin to feed the results to the sys­tem. I fig­ure I am going to use the nose-xunit plu­gin and some cus­tom XSLT for now.

One thing I need to fig­ure out is if the django-markdown plu­gin allows for rel­a­tive %url% links within a block of text so we can cross-link test­cases, I may write a cus­tom tem­plate tag.

Edit: Addi­tion­ally, I just com­mit­ted a change to remove all notion of “com­po­nent” from the sys­tem. We decided that a test case could have any num­ber of com­po­nents, or none at all, and that it was more log­i­cally con­sis­tent to track those as tags-in-the-cloud. For exam­ple, a given test case might be tagged “gui, regres­sion, smoketest, per­for­mance” or “smoke, stor­age, gui” etc. Being more flex­i­ble with sort­ing and orga­ni­za­tion was our goal.

With the much-appreciated help of Brandon Barry (with whom I just happen to work) - there's been a needed update to the testbutler code base I couldn't get to - some highlights: Cleaned up the CSS, moved to blueprint for the larger portion of the CSS and the start of jQuery usage for the ...