… And the case of obsessive optimization. A little while ago, I posted a small snippet of code that was designed to generate data files of a given size, based off a seed very quickly (article here). The goals of this code is/was the following:
Generate large amounts of semi-random data quickly
Data generation can [...]
Fixes a minor issue with python config file parsing.
Next up, hierarchical YAML files!
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 javascript [...]
As a long-time automation-engineer/test-focused guy I’ve pondered the great existential question of “how much testing” is enough for awhile.
More recently, I’ve started focusing on the cost of not testing a product.
Take for example, Figure 1:
Let’s take a second for terminology:
(A) Unit tests: These are tests focused on developer and maintainer productivity. These are “close to [...]
… Or, learn to laugh at my total inability to do web design, and lack of django-fu
So, following up (albeit slowly) on my “Decent test case tracking/registration” post, I’ve actually managed to cobble together a google code project, and a rudimentary django application.
Right now, it’s in sub-prototype stages. I’ve done a semi-production deployment internally [...]
Peer-to-Peer systems aren’t something new. Things like Bittorrent, AllMyData Tahoe, and others have been using it for file storage for some time.
Still others use the distributed-worker methodologies to do work parceling – they register with the system, and the system hands out chunks of work without factoring in client speed/etc (e.g. distributed.net).
What if you combined [...]
So, I find myself using more and more YAML lately via the pyyaml package. When I was writing nose-testconfig my “preferred” format was/is YAML.
Now, an interesting thing I’ve noticed about all of the test configurations I am developing/working with is that they have a lot of “shared” attributes (that change infrequently) and a good number [...]
Recently, there was a thread on the testing-in-python mailing list around a proposal for a new tool called “Pythoscope” (discussion here).
Pythoscope’s mission – from the website is: “To create an easily customizable and extensible open source tool that will automatically, or semi-automatically, generate unit tests for legacy systems written in Python.” To which my [...]
Following up on my “Finding Python people is hard” I figured I’d send the call out again.
We’re looking for local-to-massachusetts (we’re in Acton, MA) people who are interested in joining a dynamic, quality-focused test/automation team. Ideally, candidates are fluent in both testing (areas may include: performance, regression, web, streaming video, storage) and Python programming.
If [...]
Something that’s been a thorn in my side for some time has been a distinct lack of open, flexible and rational test case tracking tools. Many testing groups simply use spreadsheets to track thing (this doesn’t scale) and still others use tools that are proprietary/don’t handle automated tests/are overly static.
Driving into work today/in the shower [...]
|
Planet Python
