PlanetJava
Custom Search

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

Re: Test cases that are inconclusive

Subject: Re: Test cases that are inconclusive
Date: Mon, 24 Feb 2003 09:13:04 +0100 (MET)
>   I think that if you won't be able to get window system working
>   via tool like Xvfb, as Scott suggests, the best way is to divide
>   your tests into two groups. You can mark each test class of particular
>   group either using a specific prefix (like GUITest) or use subclassing
>   or similar mechanics. 
What we have successfully done is to wrap environment-specific tests in a
TestSuite. This suite will throw a test failure in run(TestResult) if the
environment is not available. Thereby you have only one failure for a whole 
suite
failing. 
A similar approach would be to check for the availability of the environment
within suite().
Johannes
Appropriate test suites can be created 
>   automatically, basing on these marks (using either test class names 
>   or reflection).
>   Using this approach, you won't forget to include specific tests
>   in to your test suites.
> 
>   Just 2c.
> 
>   With kind regards,
>   KIR
> 
> -- 
> Kirill Maximov aka KIR
> [email protected] | http://www.maxkir.com/
> St.Petersburg, Russia
> 
> 
> 
> 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/ 
> 
> 
-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
------------------------ 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