From: Robert Klemme Date: 2013-04-09T17:48:46+09:00 Subject: Re: Accessing global variable in Unit Tests --000e0ce00970f1822e04d9e99e4d Content-Type: text/plain; charset=ISO-8859-1 On Tue, Apr 9, 2013 at 10:13 AM, T- Di wrote: > My understanding was that the new test-unit uses the startup > initialization and shutdown methods. > I don't think so. Also, the "new" test-unit seems tobe the old Test::Unit refurbished and Ruby 1.9* now comes with minitest: http://rubygems.org/gems/test-unit http://rubydoc.info/gems/test-unit/2.5.4/frames I used the standard Test::Unit (minitest) and it worked with #setup and #teardown as indicated above. In any case I'm starting to think that the approach I'm using is not the > best way to handle this. What I'm trying to do is to setup the execution > of several Watir test cases, using each unit test as a contained for a > small subset of steps & validations. I know this is not the objective of > unit tests, but couldn't find a better way to handle this in a > continuous integration environment such as Hudson. > Well, if it's a test then why not? Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ --000e0ce00970f1822e04d9e99e4d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, Apr 9, 2013 at 10:13 AM, T- Di <lists@ruby-forum.com> wrote:
My understanding was that the new test-unit uses the start= up
initialization and shutdown methods.

Well, if it's a test then why not?
Kind regards

robert
--000e0ce00970f1822e04d9e99e4d--