gov.nih.nci.cagrid.testing.system.haste
Class JVMStoryRunner

java.lang.Object
  extended by gov.nih.nci.cagrid.testing.system.haste.JVMStoryRunner

public class JVMStoryRunner
extends java.lang.Object

JVMStoryRunner facilitates the execution of Stories in their own processes, and thus in their own JVM. runStoryBook() will break the book into its component Stories, and main() is responsible for parsing the classname (passed in via exec()) and instantiating and running the Story.


Constructor Summary
JVMStoryRunner()
           
 
Method Summary
protected static void doRun(Story story)
          Create a test result and execute the Story
static void main(java.lang.String[] args)
          When executed standalone, this class accepts the classname of a Story to execute.
static void runStoryBook(StoryBook book)
          Given a StoryBook, execute and report on the success of each Story within.
static void runStoryBook(StoryBook book, java.io.OutputStream out)
          Given a StoryBook, execute and report on the success of each Story within.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

JVMStoryRunner

public JVMStoryRunner()
Method Detail

main

public static void main(java.lang.String[] args)
When executed standalone, this class accepts the classname of a Story to execute.


doRun

protected static void doRun(Story story)
Create a test result and execute the Story


runStoryBook

public static void runStoryBook(StoryBook book)
Given a StoryBook, execute and report on the success of each Story within. Each story is to be executed as a separate process, which allows each Story to execute within its very own JVM, minimizing static interaction between Stories.

Parameters:
StoryBook - The StoryBook object to execute.

runStoryBook

public static void runStoryBook(StoryBook book,
                                java.io.OutputStream out)
Given a StoryBook, execute and report on the success of each Story within. Each story is to be executed as a separate process, which allows each Story to execute within its very own JVM, minimizing static interaction between Stories.

Parameters:
StoryBook - The StoryBook object to execute.
out - The output stream to do "console" reporting on