From: John Miller <jfmiller28@...>
Date: 2007-05-04T01:11:39+09:00
Subject: Re: Testing Thread and sleep

Brian Candler wrote:
> On Thu, May 03, 2007 at 11:54:37AM +0900, John Miller wrote:
>> either.
> I suggest you post your code; modify it so the process it calls via 
> popen is
> "sleep 15" or something like that.
> 
> I've never had problems testing threads; but I *have* had problems when
> testing code which forks another process (which may include popen).
> 
> The problem was that the child process inherited all the Test::Unit 
> stuff,
> including its atexit handler. I think the solution was to call exit! at 
> the
> end of the child, but I can't remember exactly.

Actually popen is easy to get around.  I rewrote it for the test simply 
return a StringIO like object instead of a new process.  I can test the 
process that is called separately.

Per request here is the code in question

This is the method I'm testing:

  #Attempt to kill the process 'pid' after
  #'time' seconds.
  def terminate_process_after(pid,time)
    Thread.new do
      sleep time
      begin
        cross_platform_end_process(pid)
      rescue
      end
    end
  end

John



-- 
Posted via http://www.ruby-forum.com/.