I’m a big fan of spreading my desktop over as many monitors I can find. When I’m working from home, this usually entails four monitors, each with 1920×1200 resolutions (made possible due to the excellent software MaxiVista, which I highly recommend). When I’m travelling or working on a client’s site, I’ll typically have to go back down to just my laptop display. One thing that has always bugged me though is when applications decide to position themselves at their last launched coordinates, even though that desktop location no longer exists. I decided to do something about it today, and wrote a little Python script to move windows that are offscreen back to the main desktop, provided below.
Continue reading ‘Fix Window Placements’
Archive for November, 2007
What I’m talking about it here is documenting test evidence or sign-offs, the fact that some user is verifying that they have tested the defect/enhancement/whatever in either a particular environment, eg your UAT env, or in a particular manner, eg regression testing, and the issue has passed, failed, or, testing is not required at all in this configuration. I’m not trying to provide support for actually running the test or how to do the test - you get that in tools like Quality Center and Rational test tools..
There are two ways to do this IMHO. Firstly, have a worflow that contains steps for each of the test environments you are interested in. Alternately, you can use linked sub-tasks, of type Test Evidence. Both ways have their pros and cons. More detail in reverse order…
One of JIRA’s shortcomings is its inability to produce any sort of diagram of the workflows. Looking at the text representation of a workflow is not particularly enlightening:
