Web front-end test frameworks or test methods

A while back I spent some time evaluating unit test frameworks from front-end web testing. A key driver is the need to handle JavaScript forms.

Here are some thoughts on those test frameworks :

- PHPUnit : Good for back-end work, but weak with front-end (browser) work

- SimpleTest : Same as PHPUnit

- Watir : Very mature and popular browser test app, but requires knowledge of Ruby scripting language

- IeUnit : Not quite as popular as Watir, but mature IE test framework. Scriptable in JavaScript

Improving performance with multi-threading on a multi-core CPU

The other day I was downloading several podcasts from the net, while doing an expensive rsync across my slow home network. My dual core CPU was showing 50% on one CPU, about 0% on the other, and my network was shown at about 1%.

My iTunes had a "download multiple streams" checkbox that was unchecked. I thought running multiple streams might actually slow things down due to thrashing/context switching, but I checked it to give me multiple streams.


Diversification with long-term bonds and commodities

Lately, I've been looking to increase the diversification in my retirement portfolio by investing in both commodities AND long-term bonds.

Crazy? Aren't these diametrically opposed views? Commodities love inflation, just like long-term bonds hate inflation.

It's hard to say where inflation is headed, although at least relative to now it seems likely to go up. But how much more inflation can we expect, and more importantly, now much of that is already priced in long-term bond prices.

Building Git on Red Hat-based systems

I had a case where I had to build Git on an older Red Hat based system. Unfortunately, the system was so old that yum wasn't really supported. So I had to install the needed libraries (RPMs) "by hand" via rpm -i. There was one package that I had to update via rpm -U.

On my rather bare system, I found I had to install the following RPMs to get Git to compile :


Migrating to a 64-bit operating system (OS)

When upgrading servers, you may encounter this question : Should we stay at at 32-bit OS, or 'upgrade' to a 64-bit OS?

To me, the big advantage of a 64-bit OS is the ability to address (use) more than 4 gigabytes of RAM. I sometimes bump into that limit on my desktop,
so I think it's best to have a 64 bit OS for servers.

Larger memory space isn't the only advantage, however. From Wikipedia :


Spell checking source code

I'm not sure of the cost/benefit of spell checking of source code, but there seem to be a couple cheap/free utilities that can help with this.

Free Python package :

Commercial shareware - $59.99 (Windows)

Another commercial shareware version - $39.99 (Windows)

Here's one man's experience checking Java source code with a "generic plain English" spell checker :


Git patch tutorial

I had some patches in one Git repository that I wanted to apply to a different repository. Here's a useful link I found on this :


Here's what I did.

First, copy the original repository you want to get patch from. This may not be necessary in all cases, but in my case the original repository was on another machine, so this just puts everything on the same machine.

    $ git clone ssh://me@example.com/repos/origRepo
    $ cd origRepo

OVF - Open Virtualization Format

If you're into computer virtualization, you should probably be familiar with OVF.

The "Open Virtualization Format" is a supposed standard for interchanging VMs between vendors (VMware, Microsoft, VirtualBox etc.) Here's a good overview of the format :


Most of my experience with virtualization has been with VMware, Xen, Virtual PC and recently with VirtualBox on the desktop.

I wanted to see how OVF might work, so I found this minimal OVF version of Solaris :


Git difftool and vimdiff

For the most part, I use TkDiff as the Git difftool when working under X Windows. TortoiseGit also has a nice GUI diff tool for when I do occassional work on Windows.

However, when working in a Linux "terminal" environment, your Git difftool choices seem to be limited to vimdiff. This is OK, but most of the color schemes under vimdiff are terrible.

I recommend using a vimdiff friendly color scheme like "greens" which is described here :

Here's how to set yourself up to use vimdiff as Git's difftool.



Subscribe to luhman.org RSS