PlanetJava
Custom Search

java-junit-user
[Top] [All Lists]

Re: Test cases that are inconclusive

Subject: Re: Test cases that are inconclusive
Date: Sun, 23 Feb 2003 11:41:50 -0500
Or, perhaps you can configure your cron job to run with a "headless" 
setup, where there is a Windowing system that you can't actually see.
David
J. B. Rainsberger wrote:
>Why would the tests be inconclusive? If the environment is bad when
>running the tests, then the tests should detect that by signaling
>errors. It would be nice if those errors clearly stated, "Could not
>find window system. Not running tests."
>
>Perhaps you should customize the Test Runner to check for the
>availability of a window system, then refuse to run the tests, if
>needed.
>
>So said  Linus Tolke  on  2/23/2003 --------------------
>
>  
>
>>How do I signal to the JUnit framework that the result of the test is
>>inconclusive?
>>    
>>
>
>JUnit does not provide this. You would have to build it. You would
>change TestResult, TestListener and the TestRunner, I think.
>
>Good luck.
>
>
>J. B. Rainsberger,
>President, Diaspar Software Services
>Let's write software that people understand.
>http://www.diasparsoftware.com/
>telephone: +1 416 791-8603
>All correspondence (c) 2002 Diaspar Software Services.
>If you want to use it, just ask; don't steal.
>
>
>
>To unsubscribe from this group, send an email to:
>[email protected]
> 
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
>
>
>  
>
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/5cFolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
[email protected]
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
msgmiddle
<Prev in Thread] Current Thread [Next in Thread>
Current Sitemap | © 2012 planetjava | Contact | Privacy Policy