In the wise words of @stahnma,
“Everybody has a testing environment. Some people are lucky enough to have a totally separate environment to run production in.”
Thankfully, the project I’m working on has multiple environments: production (the most recently-released version), staging (for pre-release testing), dev (for dev team use and testing), and multiple review apps (for feature validation). Read more on Avoid Careless Production Mistakes with Custom Scripts…
Automation is good. Performing tasks manually is bad. Performing tasks manually is especially bad when the tasks are annoying. Let’s use a Ruby script to alleviate the pain of an annoying task.
Today’s annoyance: testing and working through the kinks of a brittle, ugly data import process.
We are planning to deploy Fedora Commons into our system soon. Fedora will help facilitate sharing data across a number of systems, including ours. Until now our system data has been stored in MySQL and on the filesystem; when we deploy Fedora, we also need to import the existing data into it. Future updates will go into Fedora as they happen.
The Original Process
We already have a script to import the data into Fedora, but before doing so, we’d like to test the import locally. Below is a picture that gives a rough idea of what must happen to run the test.
Read more on Script Away Your Annoyances – Testing a Data Import Process…
Tmux is a powerful terminal multiplexer, and its built-in support for scripting allows you to create new features according to your own workflow.
I spend most of my day in Tmux, at the command line, grepping through codebases and editing files with Vim. I copied and pasted or re-typed file names for a long time before I realized how irritated I was that I couldn’t merely click on a file name and immediately open that file to the given line.
An IDE would have that functionality, and being firmly in the camp of command line as IDE, I set out to right this wrong.
Read more on An Introduction to Scripting Tmux Key Bindings…
Recently I’ve been working on a .NET app that communicates with multiple internet end points. Each end point is a data collector, and numeric data is retrieved over these connections in real time.
It is important for the app to be able to do some analysis of the data, such as minimum and maximum value, or the rate of change of a value. In order to write meaningful system tests over this functionality, I needed to simulate the data that will be generated by the end points.
Read more on Real-time Generation of Numeric Data Fixtures in IronPython…