Software tester, MIDI file artisan, trombonist, euphist
The CANYON.MID simulator
Want to relive the moment you first heard the dulcet FM synthesizer tones of the Yamaha OPL3 on your fancy new multimedia computer with Windows 3.1? Take a Trip Through the Grand Canyon again at http://canyonmid.com!
Special thanks to:
Categories: Composing.
My pull request was accepted, so random credit card type and number generation is now available in the Forgery gem!
Forgery(:credit_card).type # => "Visa" Forgery(:credit_card).number # => "4539750423451972" Forgery(:credit_card).number(:type => 'Visa', :length => 13) # => "4556180133982"
A few interesting things I picked up along the way:
Hans Peter Luhn, responsible for at least one number in your wallet
The anatomy of a credit card number (validation of credit card numbers always seemed like magic to me, but not any longer!):
6011475432471140
choice, has been deprecated. Thankfully, it was simply renamed to sample, which is available in backports.Test::Unit (which I’m more familiar with), but with a more human-readable syntax. As a result, you end up with more meaningful tests and test failures, because behaviors are being defined instead of functions.Finally, big props to Graham King and Celestino Gomes, whose knowledge and code I borrowed heavily from.
Categories: Development, Testing.
When I attended CAST 2011 this year, I was given a really neat opportunity: to present! I selected Sinatra as my topic, for a few reasons:
The presentation (in 3 parts) went something like this:
Since the audience was potentially a mix of coders, non-coders, etc., I wanted to lay some groundwork, including:
An early idea was to play “Final Countdown” while coding
Next, I gave a live coding demonstration (I’ve since been told that I was…brave for trying this). There were four distinct steps:
I shared 3 examples where Sinatra saved the day:
An e-commerce payment gateway that we had to work with was in many respects a “black box”, and it was drastically limiting our ability to test. We understood how the requests and responses worked well enough to build a replica in Sinatra, however, giving us the testability features we needed, including:
The diverse set of tools used by my team at Interactive Partners led to an unfortunate case of information siloing, but thankfully they all had APIs, so a Sinatra application named iP Relay was created to help “glue” them all together, for example:
> cap deployBotsworth: David Stamm deployed 3.16.1 (023c968) to SHO productionBug #1941 (a bug that will live in infamy) — Fixed incorrect link URL. [bug: 1941, status: resolved]
Screenshot of the "Testing Test"
Finally, the slides shown to the audience, for your viewing pleasure:
Categories: Testing.
+-------+-------+-----------+
| tablr | is | a |
+-------+-------+-----------+
| 23 | line | Sinatra |
| app | that | generates |
| rad | ASCII | tables |
+-------+-------+-----------+tablr is a lightweight, quick ‘n dirty interface to the main capabilities of TJ Holowaychuk’s Terminal Table gem. I built it because I like pasting snippets of relevant SQL tables, CSV files, or URL parameters (from Fiddler’s WebForms view) into bug reports (Bugzilla comments are plain-text, and in a fixed-width font), for example:
Parameters sent to http://api.twitter.com/1/statuses/home_timeline.json:
+----------------------------+--------------------+
| name | value |
+----------------------------+--------------------+
| max_id | 113545308612464640 |
| count | 21 |
| include_entities | 1 |
| include_available_features | 1 |
| contributor_details | true |
| pc | true |
+----------------------------+--------------------+
If you’re a Bugzilla user in particular, maybe you’ll find it useful, too!
Source code available on GitHub.
Categories: Development, Testing.