BenCurtis.com

I have just pushed out RaPT v0.2.1. New in this release is the ability to search the Rails plugin directory from the command line.

For example, rapt search authenticated would return you a list of plugins matching that search from the directory, with links back to the directory for more info and with URLs to the subversion repositories. The repository URLs can be used as the argument for rapt install [URL]. Now any plugin (that’s listed in the directory — 395 of them at the moment) is easily accessible without having to discover or even open a web browser.

Install via gem install rapt or head to the RaPT site to download a copy.

This is fun. I recently discovered how to blog with TextMate, and I’m loving it. Now if I could just edit the slug, I’d be in blogging heaven.

I just pushed out a minor update Tesly Jr. that improves the navigation of test run results. Now instead of linking back to the test plan when viewing the details of a test run, the links take you to run-specific information for that test plan. In other words, you can now drill down to the result for each test case for all of your test run history.

As requested on the Ruby Talk mailing list, you can now receive emails for failing test cases from Tesly Jr. If you specify on the Profile page that you’d like to receive email notifications, you will receive an email any time a test run includes a test plan that has a failing test case.

Now there is no excuse to not use Tesly Jr. for your continuous integration! :)

Tesly Jr. is an HTML test reporter for automated test frameworks. The first environment to be supported is Ruby’s Test::Unit, complete with a plugin for Ruby on Rails. This Rails plugin can be dropped in to a Rails project to easily add automated reporting to Tesly Jr.

What does this do for you? Well, it provides a pretty GUI interface to your test results. :) It also provides an RSS feed that is updated with the pass percentage of your tests every time you run them. In that way, it’s a good fit for continuous integration systems. Finally, once your test plans and test cases have been created by running your tests (via Rake, as usual, for Rails developers), you can add descriptions to the test plans and test cases to help document what you are testing and why.

Now you can brag to your friends about how many tests you have in your app, or show your clients and customers that you actually have tests. :)

I’d like to support other testing frameworks, like jUnit, etc. To that end, the reporting interface is simple HTTP, so any testing framework that allows for a custom reporter and can send HTTP POST requests can send test result reports to Tesly Jr. I’ll put up some info about how to construct that request at the site eventually, but until then you can contact me for info about how to do it. I’ll be happy to get more frameworks supported by helping you build hooks for your favorite one.