Hi all,
How about having a main method in all testcases with a default ui so
that each test case prgram can be run independently without the need of
running all the test cases at once. Also inc ase someone is not
connected to the net (pretty common here in India!!!) he could avoid
running those test cases. Typcially a developer is making some changes
nad he is essentially only interested in seeing whether his
changes/enahcenments are working or not so initially it would be nice
for him to be able to test out only a particular test case rather than
the whole suite.
So is it possible to just add the following in all the test cases:
public static TestSuite suite()
{
return new TestSuite(<class-name>.class);
}
public static void main(String[] args)
{
new junit.awtui.TestRunner().start(new String[]
{<class-name>.class.getName()});
}
Regards,
Dhaval Udani
Senior Analyst
M-Line, QPEG
OrbiTech Solutions Ltd.
+91-22-28290019 Extn. 1457
-----Original Message-----
From: somik [mailto:so...@ya...]
Sent: Sunday, January 26, 2003 5:13 AM
To: htmlparser-announce; htmlparser-developer; htmlparser-user
Cc: somik
Subject: [Htmlparser-developer] Integration Release 1.3-20030125 is out
Hi Folks,
The next integration release is out. From the change log :
Integration build 1.3 - 20030125
--------------------------------
[1] HTMLCompositeTagScanner now takes an array of match strings
[2] toHTML(HTMLRenderer ...) was replaced by UrlModifyingVisitor
[3] Fixed NullPointerException in HTMLScriptTag.toString()
[4] Fixed bug in HTMLStringNode (breaking up empty lines into seperate
string nodes)
[5] Fixed thread safety issue and introduced parser helpers
[6] Fixed bug 664404 - spewing incorrect line breaks in
HTMLRemarkNode.toHTML()
[7] Added assertXmlEquals() in HTMLParserTestCase
[8] Added better option tag support
[9] Replaced instanceof with getType() mechanism - much faster
[10] Incorporated NodeList instead of Vector in HTMLCompositeTag
[11] Added HTMLRemarkNode support in Visitor
[12] Fixed bug 673379 (infinite loop on encountering links like
".someurl.html")
Among the notable additions is assertXmlEquals() - this is present to
enable
us to perform xml testing. This method actually creates the parser and
performs a node for node comparison.
Reconstruction has improved a lot - you will find that the parser now
does
not add unnecessary line breaks - and preserves the html as it came in.
One significant addition is the use of NodeList instead of Vector. The
integration has been performed, so there should be a significant
performance
increase - check
http://htmlparser.sourceforge.net/performance/simpleEnumerationPerforman
ce.h
tml
In the coming week, we will be setting up a wiki on sourceforge, where
we
can collaboratively create documentation - hopefully that will finally
take
the burden out of the documentation process.
Regards,
Somik
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Htmlparser-developer mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/htmlparser-developer
|
