Snipplr

(Ruby) Watchr config for use with PHPUnit - noah

Thu, 31 Mar 2011 14:28:22 GMT

A simple [Watchr](https://github.com/mynyml/watchr) config for running PHPUnit tests. This will run a [Pake](https://github.com/indeyets/pake/wiki) task called "test" and ring the system bell if the task fails. *Ringing the system bell* is especially nice when running inside a GNU Screen session. *Installation* To install you need [RubyGems](http://rubyforge.org). Then type: sudo gem install watchr

(Ruby) analysis of Hudson JUNit logfiles - noah

Sat, 20 Nov 2010 17:15:44 GMT

assuming you are standing in`$HUDSON_HOME/jobs/job_foo/builds/123`

(Ruby) Howto set up a Rake task to start and stop the Selenium-RC server - noah

Mon, 08 Feb 2010 23:01:08 GMT

(Ruby) Howto set up a Rake task to run Cucumber features and generate reports - noah

Mon, 08 Feb 2010 22:41:45 GMT

Note that Rake is slower than just running `cucumber`

(Ruby) Howto set up a Rake task to run RSpec spec docs - noah

Mon, 08 Feb 2010 21:23:31 GMT

A `rake :spec` task, is created by default just from including the RSpec rake module. The way to *stop RSpec tasks from failing* the entire Rake job when a test barfs, is by setting `fail_on_error` to false.

(Ruby) How to call JavaScript in the Application Under Test, from Selenium - noah

Thu, 17 Sep 2009 13:14:43 GMT

When writing functional tests with Selenium, it is often convenient to call JavaScript functions and methods, that are part of the Web application you are testing. After all, Selenium is a functional testing framework for Web UI and most of the exciting bits of Web UI are JS (sorry, all you CSS hackers, but them's the facts). The problem is that it's not immediately obvious how you can access the DOM of the Application Under Test (AUT). Selenium Core (in which all Selenium tests execute) is a frame set, and if you simply try to call your JavaScript with `getEval`, you'll get an error because `getEval` references Selenium Core's DOM, not the DOM of the AUT. Fortunately the answer is simple. Use `this.browserbot.getCurrentWindow()` to get a reference to the `window` object in *your* DOM. Then you can execute any of the JS that lives in your page, right from Selenium! This example uses the Ruby driver, but the principle is the same regardless of which language you use.

(Ruby) factory girl example - jnunemaker

Tue, 28 Oct 2008 23:58:50 GMT

(Ruby) make Ruby strings behave like files - cczona

Thu, 13 Mar 2008 18:38:19 GMT

This is handy for testing, when you need to simulate an open file or open URI. Why, and the Pickaxe book, have better examples

(Ruby) Verifier objects - pmccann

Sat, 12 May 2007 16:39:41 GMT

Niiice... (stolen from linked site via planetrubyonrails.com)

(Ruby) fixture_file_upload Example - tjstankus

Sun, 26 Nov 2006 03:24:28 GMT

fixture_file_upload is another nifty Rails testing feature. It allows you to create "MIME-encoded content that would normally be uploaded by a browser input field." (Part in quotes straight from Agile Web Development with Rails, v2). Put your files to test in test/fixtures/files. You have to create the 'files' directory; rails doesn't do it for you.

(Ruby) ARTestHelper - Catfish

Wed, 20 Sep 2006 03:42:34 GMT

(Ruby) Test for required attributes - tjstankus

Sat, 08 Jul 2006 20:17:13 GMT

A fairly DRY way to test for required attributes of a model. It's sort of an alternative to fixtures. It breaks the one-assertion-per-test rule that some people favor. Drop in your unit test and edit as necessary. A better (yet not quite perfect) approach: http://johnwilger.com/articles/2005/12/07/a-bit-of-dryness-for-unit-tests-in-rails