Menu
▾
▴
junit-devel — junit developers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(80) |
Nov
(42) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(11) |
Feb
(50) |
Mar
(70) |
Apr
(102) |
May
(28) |
Jun
(45) |
Jul
(14) |
Aug
(75) |
Sep
(17) |
Oct
(15) |
Nov
(11) |
Dec
(4) |
| 2003 |
Jan
(16) |
Feb
(19) |
Mar
(21) |
Apr
(20) |
May
(29) |
Jun
(7) |
Jul
(5) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(3) |
| 2004 |
Jan
(5) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(7) |
Aug
(1) |
Sep
(6) |
Oct
(6) |
Nov
(1) |
Dec
(2) |
| 2005 |
Jan
(4) |
Feb
(4) |
Mar
(15) |
Apr
(1) |
May
|
Jun
(4) |
Jul
(6) |
Aug
(6) |
Sep
|
Oct
(4) |
Nov
(2) |
Dec
(4) |
| 2006 |
Jan
|
Feb
(91) |
Mar
(47) |
Apr
(7) |
May
(4) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(5) |
Oct
(36) |
Nov
(95) |
Dec
(12) |
| 2007 |
Jan
(11) |
Feb
(31) |
Mar
(45) |
Apr
(11) |
May
(9) |
Jun
(1) |
Jul
(146) |
Aug
(15) |
Sep
|
Oct
(3) |
Nov
(6) |
Dec
(1) |
| 2008 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(2) |
Aug
(19) |
Sep
(1) |
Oct
(10) |
Nov
|
Dec
(8) |
| 2009 |
Jan
(3) |
Feb
(1) |
Mar
(4) |
Apr
(8) |
May
(5) |
Jun
(4) |
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
(13) |
Nov
(13) |
Dec
(4) |
| 2010 |
Jan
(1) |
Feb
(2) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
(1) |
Feb
(4) |
Mar
(3) |
Apr
(4) |
May
|
Jun
(12) |
Jul
(16) |
Aug
(4) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
|
From: David S. <sa...@mi...> - 2006-03-15 19:37:15
|
Curt Arnold wrote:
> Looks like we have found a culprit. There was a lot of Junit related
> traffic on ant-dev last week, though I couldn't pick this particular
> issue out of the noise and there did not appear to be a bug report
> filed against it. Will follow up with the apr-dev mailing list.
Good to know. Thanks,
David Saff
|
|
From: Curt A. <ca...@ap...> - 2006-03-15 19:18:11
|
On Mar 15, 2006 on ge...@gu..., at 12:59 PM, Bill Barker wrote: > > From your commit messages, I believe that it's the same Ant bug > that was > killing commons-collections last week. The short version is that > when Ant > auto-detects JUnit-4, it doesn't look for the static suite() > method, and > just assumes that you've defined all of your tests with Annotations. > Looks like we have found a culprit. There was a lot of Junit related traffic on ant-dev last week, though I couldn't pick this particular issue out of the noise and there did not appear to be a bug report filed against it. Will follow up with the apr-dev mailing list. |
|
From: David S. <ds...@us...> - 2006-03-15 18:20:37
|
Update of /cvsroot/junit/junit In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3437 Modified Files: README.html Log Message: README up to date for 4.1 Index: README.html =================================================================== RCS file: /cvsroot/junit/junit/README.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -d -r1.12 -r1.13 --- README.html 16 Feb 2006 08:29:36 -0000 1.12 +++ README.html 15 Mar 2006 18:20:05 -0000 1.13 @@ -4,13 +4,13 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="Author" content="Erich Gamma, Kent Beck, and David Saff"> - <title>JUnit 4.0</title> + <title>JUnit 4.1</title> </head> <body> <h1> <b><font color="#00CC00">J</font><font color="#FF0000">U</font><font color="#000000">nit -4.0</b></h1> +4.1</b></h1> <br>Brought to you by <a href="http://www.threeriversinstitute.org">Kent Beck</a>, Erich Gamma, and <a href="http://pag.csail.mit.edu/continuoustesting">David Saff</a>. @@ -20,7 +20,7 @@ <br>(see also <a href="http://www.junit.org">JUnit.org</a>) <hr WIDTH="100%"> -<br>2/15/06 +<br>09 Mar 2006 <p>JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks. <ul> @@ -42,10 +42,21 @@ <a href="#Known Defects">Known Defects</a></li> </ul> - - <h2> -<a NAME="Summary of"></a>Summary of Changes with version 4.0</h2> +<a NAME="Summary of"></a>Summary of Changes with version 4.1</h2> +<p> +<ul> +<li>Bug fix: listeners now get a correct test running time, rather than always being told 0 secs. +<li>The @RunWith annotation is now inherited by subclasses: +all subclasses of an abstract test class will be run by the same runner. +<li>The build script fails if the JUnit unit tests fail +<li>The faq has been updated +<li>Javadoc has been improved, with more internal links, and package descriptions added (Thanks, Matthias Schmidt!) +<li>An acknowledgements.txt file has been created to credit outside contributions +</ul> +</p> + +<h2>Summary of Changes with version 4.0</h2> <p> The architecture of JUnit 4.0 is a substantial departure from that of earlier releases. Instead of @@ -65,13 +76,13 @@ </tr> <tr> -<td><tt>junit-4.0.jar</tt></td> +<td><tt>junit-4.1.jar</tt></td> <td>a jar file with the JUnit framework</td> </tr> <tr> -<td><tt>junit-4.0-src.jar</tt></td> +<td><tt>junit-4.1-src.jar</tt></td> <td>a jar file with the source code of the JUnit framework</td> </tr> @@ -112,20 +123,20 @@ Below are the installation steps for installing JUnit: <ol> <li> -unzip the junit4.0.zip file</li> +unzip the junit4.1.zip file</li> <li> -add<i> </i><b>junit-4.0.jar</b> to the CLASSPATH. For example: -<tt> set classpath=%classpath%;INSTALL_DIR\junit-4.0.jar;INSTALL_DIR</tt></li> +add<i> </i><b>junit-4.1.jar</b> to the CLASSPATH. For example: +<tt> set classpath=%classpath%;INSTALL_DIR\junit-4.1.jar;INSTALL_DIR</tt></li> <li> test the installation by running <tt>java org.junit.runner.JUnitCore org.junit.tests.AllTests.</tt></li> <br><b><font color="#FF0000">Notice</font></b>: that the tests are not -contained in the junit-4.0.jar but in the installation directory directly. +contained in the junit-4.1.jar but in the installation directory directly. Therefore make sure that the installation directory is on the class path </ol> -<b><font color="#FF0000">Important</font></b>: don't install the junit-4.0.jar +<b><font color="#FF0000">Important</font></b>: don't install junit-4.1.jar into the extension directory of your JDK installation. If you do so the test class on the files system will not be found. <h2> @@ -133,7 +144,7 @@ To get started with unit testing and JUnit read the article: <a href="doc/cookbook/cookbook.htm">JUnit Cookbook</a>. <br>This article describes basic test writing using JUnit 4. -<p>You find additional samples in the junit.samples package: +<p>You find additional samples in the org.junit.samples package: <ul> <li> SimpleTest.java - some simple test cases</li> @@ -166,7 +177,6 @@ <h2><a NAME="Known Defects"></a>Known Defects</h2> <ul> <li>Multi-dimensional arrays are not processed correctly by assertEquals.</li> -<li>The time printed by JUnitCore after running tests is always 0.</li> </ul> <hr WIDTH="100%"> |
|
From: David S. <sa...@mi...> - 2006-03-15 18:04:17
|
Curt Arnold wrote:
> BUILD FAILED
> /x1/gump/public/workspace/junit/build.xml:21: Warning: Could not find
> file
> /x1/gump/public/workspace/junit/junit/runner/Version.java.template to
> copy.
Yes. That has since been fixed in HEAD.
> You agreed to let yourself be nagged about Gump failures on
> 12-Mar-2006 and the Gump descriptor for junit was changed by
> bil...@ap.... Though the to address is unusual, maybe it is
> acceptable. Since the change occurred after the last reported
> failure, maybe it will work just fine when the next failure message
> comes along. I'll raise this on ge...@gu... and take no
> action myself.
Sounds like the right plan. Thanks,
David Saff
|
|
From: Curt A. <ca...@ap...> - 2006-03-15 18:03:40
|
On Mar 15, 2006, at 11:55 AM, David Saff wrote: > I have no knowledge of Gump nag descriptor formatting, so I'll have > to ask your help on this. How often are the nag messages sent? If > it's daily or less, then sending it to junit-devel should be fine. > Otherwise, please have it sent straight to me. Thanks, Daily messages when junit is failing to build, no messages otherwise. I'll post a request on the issue to ge...@gu.... |
|
From: Curt A. <ca...@ap...> - 2006-03-15 18:00:29
|
>> >> I have yet to receive any kind of automated nag, only personal >> nags from real people. Could something be misconfigured? Thanks, >> > I've reviewed the Gump mailing list. There were CVS problems and junit build problems reported on 09-March-2006 (http:// marc.theaimsgroup.com/?l=gump&m=114190474119176&w=2) which went into the "All dressed up and no where to go" message for undeliverable failure messages. The following fragments were significant for junit: The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/junit/gump_work/update_junit.html Work Name: update_junit (Type: Update) Work ended in a state of : Failed Elapsed: Command Line: cvs -q -z3 -d :pserver:ano...@cv...:/ cvsroot/junit \ update -P -d -A [Working Directory: /usr/local/gump/public/workspace/ cvs/junit] --------------------------------------------- cvs [update aborted]: end of file from server (consult above messages if any) --------------------------------------------- The previous day's message (http://marc.theaimsgroup.com/? l=gump&m=114181866415173&w=2) had a successful CVS checkout, but failed with: versiontag: BUILD FAILED /x1/gump/public/workspace/junit/build.xml:21: Warning: Could not find file /x1/gump/public/workspace/junit/junit/runner/ Version.java.template to copy. You agreed to let yourself be nagged about Gump failures on 12- Mar-2006 and the Gump descriptor for junit was changed by bil...@ap.... Though the to address is unusual, maybe it is acceptable. Since the change occurred after the last reported failure, maybe it will work just fine when the next failure message comes along. I'll raise this on ge...@gu... and take no action myself. |
|
From: David S. <sa...@mi...> - 2006-03-15 17:55:26
|
Curt Arnold wrote:
> The current project descriptor contains:
>
> <nag from="Gump Integration <ge...@gu...>"
> to="David Saff <sa...@mi...>" />
>
> I could change it to:
>
> <nag from="David Saff <sa...@mi...>"
> to="jun...@li..." />
>
> or post a request to the Gump mailing list to review your project
> descriptor.
I have no knowledge of Gump nag descriptor formatting, so I'll have to
ask your help on this. How often are the nag messages sent? If it's
daily or less, then sending it to junit-devel should be fine.
Otherwise, please have it sent straight to me. Thanks,
David Saff
|
|
From: Curt A. <ca...@ap...> - 2006-03-15 17:39:12
|
On Mar 15, 2006, at 10:58 AM, David Saff wrote: > Curt Arnold wrote: >> Yes. I can observe it right now. If I attempt to log in to an >> arbitrary SourceForge project >> >> cvs -d:pserver:ano...@cv...:/cvsroot/ant-contrib >> >> I get an immediate completion after hitting enter on the >> password. If I change it to: >> >> cvs -d:pserver:ano...@cv...:/cvsroot/junit >> >> I get "Unrecognized auth response from cvs.sourceforge.net: M >> PserverBackend: PserverBackend() Connect (Connection Timed Out)". > > Woah. I had never considered that this might be a JUnit-only > problem. I've followed up with SourceForge. > I'm still seeing the problem, but Gump just successfully built junit. >> When reviewing earlier Gump logs, I noticed that the junit build >> also had timed out due to CVS. Gump is currently running and >> junit has not been attempted yet, but you could review the status >> at http://vmgump.apache.org/gump/public/buildLog.html. I noticed >> that the Gump nag notices are sent to you personally, so maybe you >> have something in those that could provide info on the status of >> anonymous CVS access on previous runs. > > I have yet to receive any kind of automated nag, only personal nags > from real people. Could something be misconfigured? Thanks, > Possibly, you should have been receiving Gump failure messages just before 10-March-2006 since Gump is indicating that the start of the current success state started then. The nag element in your project descriptor is unusual, it seems to be the only one in the Gump universe that places contains < in the to address (it is common in the from address). It is also common that nag messages are sent to the development list. Since messages from non-subscribers are usually blocked for moderation, it would be good to either make the message appear to be from a current subscriber. I think using ge...@gu... (the Gump general mailing list) as a sender is undesirable since it results in spurious replies to the nag message going to their general list. The current project descriptor contains: <nag from="Gump Integration <ge...@gu...>" to="David Saff <sa...@mi...>" /> I could change it to: <nag from="David Saff <sa...@mi...>" to="jun...@li..." /> or post a request to the Gump mailing list to review your project descriptor. |
|
From: Curt A. <ca...@ap...> - 2006-03-15 17:18:05
|
On Mar 15, 2006, at 10:53 AM, David Saff wrote: > > Can you give me the fully-qualified name of the class you're > interested in? I have a class named > org.junit.internal.runners.TestClass in my local working copy, but > this doesn't have the "No runnable methods" message, and should not > be checked in. Sorry, I dropped part of the class name. If I download junit- gump-15032006.jar (or -14) from http://vmgump.apache.org/gump/public- jars/junit/jars/, unzip and grep, I get a match in org/junit/internal/ runners/TestClassMethodsRunner.class. |
|
From: David S. <sa...@mi...> - 2006-03-15 16:53:32
|
Curt Arnold wrote: > I reviewed the mailing list archive to see if there had been recent > commits to the CVS that might be related to the change of behavior. > There weren't any, but their did not seem to be any messages at all in > the archives since mid-February which seemed suspicious. You're right. There's certainly been activity on the list since 2/22, and commits within the last 24 hours. I'll have to look into this. > Should be running the stock junit task in the CVS HEAD of Ant. The > project file is > http://svn.apache.org/repos/asf/logging/log4j/trunk/tests/build.xml. > The failure occurs during the "Core" target. Thanks. I'll look into it. > Yes, either when I use Ant 1.6.5 and Junit 3.8.1 or a junit.jar from > Gump. I have not attempted to use a SVN HEAD version of Ant, though > it could be the problem. However, the test "No runnable methods" does > appear in the TestClass.class file. Can you give me the fully-qualified name of the class you're interested in? I have a class named org.junit.internal.runners.TestClass in my local working copy, but this doesn't have the "No runnable methods" message, and should not be checked in. Thanks, David Saff |
|
From: Curt A. <ca...@ap...> - 2006-03-15 16:39:13
|
On Mar 15, 2006, at 9:30 AM, David Saff wrote: > Curt Arnold wrote: >> The Gump (http://gump.apache.org) nightly builds for log4j have >> been failing for the last few nights due to a suspected change in >> the junit source code. > > Sorry about that. Let's get it fixed. > >> I attempted to check out the current CVS HEAD, but the system was >> unresponsive. > > You're not the first to be frustrated by sourceforge's glacial > anonymous cvs access over the last few months. I'm looking into > whether we can get any kind of better guarantees from SourceForge. > My apologies. > >> The lack of activity on the mailing list archive is also >> disconcerting. > > Is there a question that has gone unanswered? > No, just that it looked like there may also be technical issues with the mailing list. I reviewed the mailing list archive to see if there had been recent commits to the CVS that might be related to the change of behavior. There weren't any, but their did not seem to be any messages at all in the archives since mid-February which seemed suspicious. Has there been CVS activity in the last month, particularly in the last few days or in runners.TestClass? If not, then I might be misattributing the problem. >> I've updated the Gump metadata so that log4j builds against junit >> 3.8.1 not the CVS HEAD and should know overnight if that avoids >> the symptoms for now. > > You may want to try 4.0 (tagged r40) or 3.8.2 (tagged r382), which > are the supported release versions. > Gump has project descriptors for junit3 and junit. The junit3 project uses a release version of junit. I thought it was 3.8.1, but maybe it has been updated to 3.8.2. junit builds from the CVS HEAD. There is not a project descriptor for a junit 4 release. I bungled the update of the log4j Gump descriptor to use junit3 last night, but have hopefully fixed it now. There is a gump build in process and should know in a few hours if reverting to junit 3 suppresses the problem. >> The Gump build fails with: >> >> [junit] Testcase: org.apache.log4j.CoreTestSuite took 0.004 sec >> [junit] Caused an ERROR >> [junit] No runnable methods >> [junit] java.lang.Exception: No runnable methods >> >> CoreTestSuite.java looks like: > > [snip] > >> What I assume is happening is that one of the classes in the calls >> to addTestSuite does not contain any test methods or the >> inadvertent (and just recognized) duplication of LoggingEventTest >> is resulting in an exception that did not occur with junit prior >> to a few days ago. In either case, the "No runnable methods" >> message is of very little help in analyzing the problem. It would >> be helpful at least if the "No runnable methods" message would >> include the name of the class that was being examined for runnable >> methods. > > Yuck. Can you give me more information about the ant task that is > running the tests? I'd love to know why ant has decided to filter > out all but the least useful information provided by JUnit. Should be running the stock junit task in the CVS HEAD of Ant. The project file is http://svn.apache.org/repos/asf/logging/log4j/trunk/ tests/build.xml. The failure occurs during the "Core" target. > >> Unfortunately log4j is a bear to set up to build since it involves >> a large number of Sun and third-party dependencies. I haven't >> been able to reproduce the problem on my local machines using >> log4j jars from Gump. > > So when you run it locally, the tests appear to pass? Yes, either when I use Ant 1.6.5 and Junit 3.8.1 or a junit.jar from Gump. I have not attempted to use a SVN HEAD version of Ant, though it could be the problem. However, the test "No runnable methods" does appear in the TestClass.class file. |
|
From: David S. <sa...@mi...> - 2006-03-15 16:18:56
|
All, I've submitted a SourceForge support request about intermittent CVS pserver access: http://sourceforge.net/tracker/index.php?func=detail&aid=1450494&group_id=1&atid=200001 SourceForge believes that a similar problem was resolved on the 12th: http://sourceforge.net/tracker/index.php?func=detail&aid=1447585&group_id=1&atid=200001 At least two independent sources have complained about CVS here since the 12th. Can you confirm that your problems occurred on the 13th or later? Thanks, David Saff |
|
From: David S. <sa...@mi...> - 2006-03-15 15:30:41
|
Curt Arnold wrote: > The Gump (http://gump.apache.org) nightly builds for log4j have been > failing for the last few nights due to a suspected change in the junit > source code. Sorry about that. Let's get it fixed. > I attempted to check out the current CVS HEAD, but the system was > unresponsive. You're not the first to be frustrated by sourceforge's glacial anonymous cvs access over the last few months. I'm looking into whether we can get any kind of better guarantees from SourceForge. My apologies. > The lack of activity on the mailing list archive is also disconcerting. Is there a question that has gone unanswered? > I've updated the Gump metadata so that log4j builds against junit > 3.8.1 not the CVS HEAD and should know overnight if that avoids the > symptoms for now. You may want to try 4.0 (tagged r40) or 3.8.2 (tagged r382), which are the supported release versions. > The Gump build fails with: > > [junit] Testcase: org.apache.log4j.CoreTestSuite took 0.004 sec > [junit] Caused an ERROR > [junit] No runnable methods > [junit] java.lang.Exception: No runnable methods > > CoreTestSuite.java looks like: [snip] > What I assume is happening is that one of the classes in the calls to > addTestSuite does not contain any test methods or the inadvertent (and > just recognized) duplication of LoggingEventTest is resulting in an > exception that did not occur with junit prior to a few days ago. In > either case, the "No runnable methods" message is of very little help > in analyzing the problem. It would be helpful at least if the "No > runnable methods" message would include the name of the class that was > being examined for runnable methods. Yuck. Can you give me more information about the ant task that is running the tests? I'd love to know why ant has decided to filter out all but the least useful information provided by JUnit. > Unfortunately log4j is a bear to set up to build since it involves a > large number of Sun and third-party dependencies. I haven't been able > to reproduce the problem on my local machines using log4j jars from Gump. So when you run it locally, the tests appear to pass? |
|
From: Curt A. <ca...@ap...> - 2006-03-15 06:04:24
|
The Gump (http://gump.apache.org) nightly builds for log4j have been failing for the last few nights due to a suspected change in the junit source code. I attempted to check out the current CVS HEAD, but the system was unresponsive. The lack of activity on the mailing list archive is also disconcerting. I've updated the Gump metadata so that log4j builds against junit 3.8.1 not the CVS HEAD and should know overnight if that avoids the symptoms for now. The Gump build fails with: [junit] Testcase: org.apache.log4j.CoreTestSuite took 0.004 sec [junit] Caused an ERROR [junit] No runnable methods [junit] java.lang.Exception: No runnable methods CoreTestSuite.java looks like: /* * Copyright 1999,2005 The Apache Software Foundation. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ package org.apache.log4j; import junit.framework.Test; import junit.framework.TestSuite; import org.apache.log4j.spi.LoggingEventTest; /** * Suite of log4j class level unit tests. * * @author Curt Arnold * @since 1.3 */ public class CoreTestSuite { /** * Constructs test suite. * @return test suite * @deprecated since some tests in suite test deprecated classes. */ public static Test suite() { TestSuite s = new TestSuite(); s.addTestSuite(LoggingEventTest.class); s.addTestSuite (org.apache.log4j.pattern.NameAbbreviatorTest.class); s.addTestSuite (org.apache.log4j.pattern.PatternParserTest.class); s.addTestSuite (org.apache.log4j.rolling.helper.FileNamePatternTestCase.class); s.addTestSuite (org.apache.log4j.pattern.FormattingInfoTest.class); s.addTestSuite(org.apache.log4j.LevelTest.class); s.addTestSuite(org.apache.log4j.PriorityTest.class); s.addTestSuite(org.apache.log4j.CategoryTest.class); s.addTestSuite(org.apache.log4j.LogManagerTest.class); s.addTestSuite(org.apache.log4j.helpers.LogLogTest.class); s.addTestSuite(org.apache.log4j.LayoutTest.class); s.addTestSuite(org.apache.log4j.helpers.DateLayoutTest.class); s.addTestSuite(org.apache.log4j.TTCCLayoutTest.class); s.addTestSuite(org.apache.log4j.xml.XMLLayoutTest.class); s.addTestSuite(org.apache.log4j.HTMLLayoutTest.class); s.addTestSuite(org.apache.log4j.PatternLayoutTest.class); s.addTestSuite(org.apache.log4j.spi.LoggingEventTest.class); return s; } } What I assume is happening is that one of the classes in the calls to addTestSuite does not contain any test methods or the inadvertent (and just recognized) duplication of LoggingEventTest is resulting in an exception that did not occur with junit prior to a few days ago. In either case, the "No runnable methods" message is of very little help in analyzing the problem. It would be helpful at least if the "No runnable methods" message would include the name of the class that was being examined for runnable methods. Unfortunately log4j is a bear to set up to build since it involves a large number of Sun and third-party dependencies. I haven't been able to reproduce the problem on my local machines using log4j jars from Gump. |
|
From: Curt S. <cj...@cy...> - 2006-03-15 05:11:06
|
On Mon, 13 Mar 2006, Mat...@un... wrote: > Even migrating from cvs (with branches etc.) seems to be possible: > http://sial.org/howto/subversion/cvs-migrate/ I recently performed a large migration, and so I'm pretty familiar with it and have some tools. Since I used to use JUnit a lot back when I programmed in Java, I'd be willing to help out whoever is doing the migration; just get in touch with me directly. cjs -- Curt Sampson <cj...@cy...> +81 90 7737 2974 The power of accurate observation is commonly called cynicism by those who have not got it. --George Bernard Shaw |
|
From: <Mat...@un...> - 2006-03-13 13:39:25
|
If there are usable clients that would be a great idea. Even migrating from cvs (with branches etc.) seems to be possible: = http://sial.org/howto/subversion/cvs-migrate/ -----Urspr=FCngliche Nachricht----- Von: jun...@li... = [mailto:jun...@li...] Im Auftrag von David = Saff Gesendet: Montag, 13. M=E4rz 2006 13:55 An: J. David Beutel Cc: jun...@li... Betreff: Re: AW: [Junit-devel] cvs-timeout I've used subclipse, and it was just barely tolerable--I often ended up=20 dropping to the command line to do commits and merges. I downloaded=20 subversive last night, and I'll give it a go for a while. If it works=20 well, then I'd be more than happy to see a move to subversion. Kent,=20 Erich, your thoughts? David J. David Beutel wrote: > I'm using IDEA, which comes with JavaSVN. I'm happy with it. Two=20 > Eclipse plugins also use JavaSVN, but I haven't tried them and don't=20 > know how well integrated they are. > > Cheers, > 11011011 > > <Mat...@un...> wrote on 03/12/2006 09:55:00 PM: >> Of course, subversion is better. Wouldn't it be great to switch JUnit = >> to subversion? >> >> Btw: What client are you using? I heard, that the Eclipse clients are = >> not that good at the moment. >> >> -----Urspr=FCngliche Nachricht----- >> Von: jun...@li...=20 >> [mailto:jun...@li...] Im Auftrag von J.=20 >> David Beutel >> Gesendet: Sonntag, 12. M=E4rz 2006 23:47 >> An: jun...@li... >> Betreff: Re: [Junit-devel] cvs-timeout >> >> I've had the same problem, and better luck with SourceForge's=20 >> anonymous Subversion (so far, anyway). Also, I prefer Subversion. >> >> Cheers, >> 11011011 >> >> David Saff <sa...@mi...> wrote on 03/08/2006 08:37:41 AM: >> =20 >>> Matt, >>> >>> Anonymous pserver CVS access to SourceForge is absolutely terrible. = >>> Committers get CVS/SSH access, which is reasonably fast, so the=20 >>> people to whom SourceForge is most likely to listen are least likely = >>> to complain. I actually ended up setting up a daemon that tried to=20 >>> update every hour, so that when I sat down to develop, there was a=20 >>> good chance that I had an up-to-date version. Of course, this just=20 >>> contributed to everyone else's traffic, so there's probably a better = >>> solution somewhere. >>> >>> Sorry, >>> >>> David Saff >>> >>> Mat...@un... wrote: >>> =20 >>>> Hi *.*, >>>> >>>> =20 >>>> >>>> is it just me or do you guys also get lots of timeouts when trying=20 >>>> to synchronize with the sourceforge cvs? > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting=20 > language > that extends applications into web and mobile media. Attend the live=20 > webcast > and join the prime developer group breaking into this new coding=20 > territory! > = http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 > _______________________________________________ > Junit-devel mailing list > Jun...@li... > https://lists.sourceforge.net/lists/listinfo/junit-devel ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting = language that extends applications into web and mobile media. Attend the live = webcast and join the prime developer group breaking into this new coding = territory! http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ Junit-devel mailing list Jun...@li... https://lists.sourceforge.net/lists/listinfo/junit-devel |
|
From: David S. <sa...@mi...> - 2006-03-13 12:55:36
|
I've used subclipse, and it was just barely tolerable--I often ended up
dropping to the command line to do commits and merges. I downloaded
subversive last night, and I'll give it a go for a while. If it works
well, then I'd be more than happy to see a move to subversion. Kent,
Erich, your thoughts?
David
J. David Beutel wrote:
> I'm using IDEA, which comes with JavaSVN. I'm happy with it. Two
> Eclipse plugins also use JavaSVN, but I haven't tried them and don't
> know how well integrated they are.
>
> Cheers,
> 11011011
>
> <Mat...@un...> wrote on 03/12/2006 09:55:00 PM:
>> Of course, subversion is better. Wouldn't it be great to switch JUnit
>> to subversion?
>>
>> Btw: What client are you using? I heard, that the Eclipse clients are
>> not that good at the moment.
>>
>> -----Ursprüngliche Nachricht-----
>> Von: jun...@li...
>> [mailto:jun...@li...] Im Auftrag von J.
>> David Beutel
>> Gesendet: Sonntag, 12. März 2006 23:47
>> An: jun...@li...
>> Betreff: Re: [Junit-devel] cvs-timeout
>>
>> I've had the same problem, and better luck with SourceForge's
>> anonymous Subversion (so far, anyway). Also, I prefer Subversion.
>>
>> Cheers,
>> 11011011
>>
>> David Saff <sa...@mi...> wrote on 03/08/2006 08:37:41 AM:
>>
>>> Matt,
>>>
>>> Anonymous pserver CVS access to SourceForge is absolutely terrible.
>>> Committers get CVS/SSH access, which is reasonably fast, so the
>>> people to whom SourceForge is most likely to listen are least likely
>>> to complain. I actually ended up setting up a daemon that tried to
>>> update every hour, so that when I sat down to develop, there was a
>>> good chance that I had an up-to-date version. Of course, this just
>>> contributed to everyone else's traffic, so there's probably a better
>>> solution somewhere.
>>>
>>> Sorry,
>>>
>>> David Saff
>>>
>>> Mat...@un... wrote:
>>>
>>>> Hi *.*,
>>>>
>>>>
>>>>
>>>> is it just me or do you guys also get lots of timeouts when trying
>>>> to synchronize with the sourceforge cvs?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Junit-devel mailing list
> Jun...@li...
> https://lists.sourceforge.net/lists/listinfo/junit-devel
|
|
From: Fran H. <fra...@ie...> - 2006-03-13 10:01:14
|
I will be out of the office starting 10/03/2006 and will not return until 20/03/2006. If you have any support issues/queries please raise a 199 call and assign them to the appropriate support team listed below; CDR Support :- EIENR_ASCDRAPPS MFG Lotus Notes - EIEDN_SSLAMFGLN BARCODE - EIEDN_SSLAMFGBC Thanks alot, Fran. |
|
From: J. D. B. <jd...@ge...> - 2006-03-13 08:11:04
|
I'm using IDEA, which comes with JavaSVN. I'm happy with it. Two Eclipse plugins also use JavaSVN, but I haven't tried them and don't know how well integrated they are. Cheers, 11011011 <Mat...@un...> wrote on 03/12/2006 09:55:00 PM: > Of course, subversion is better. Wouldn't it be great to switch JUnit to subversion? > > Btw: What client are you using? I heard, that the Eclipse clients are not that good at the moment. > > -----Ursprüngliche Nachricht----- > Von: jun...@li... [mailto:jun...@li...] Im Auftrag von J. David Beutel > Gesendet: Sonntag, 12. März 2006 23:47 > An: jun...@li... > Betreff: Re: [Junit-devel] cvs-timeout > > I've had the same problem, and better luck with SourceForge's anonymous > Subversion (so far, anyway). Also, I prefer Subversion. > > Cheers, > 11011011 > > David Saff <sa...@mi...> wrote on 03/08/2006 08:37:41 AM: > >> Matt, >> >> Anonymous pserver CVS access to SourceForge is absolutely terrible. >> Committers get CVS/SSH access, which is reasonably fast, so the people >> to whom SourceForge is most likely to listen are least likely to >> complain. I actually ended up setting up a daemon that tried to >> update every hour, so that when I sat down to develop, there was a >> good chance that I had an up-to-date version. Of course, this just >> contributed to everyone else's traffic, so there's probably a better >> solution somewhere. >> >> Sorry, >> >> David Saff >> >> Mat...@un... wrote: >> >>> Hi *.*, >>> >>> >>> >>> is it just me or do you guys also get lots of timeouts when trying to >>> synchronize with the sourceforge cvs? |
|
From: <Mat...@un...> - 2006-03-13 07:51:20
|
Of course, subversion is better. Wouldn't it be great to switch JUnit to = subversion? Btw: What client are you using? I heard, that the Eclipse clients are = not that good at the moment. -----Urspr=FCngliche Nachricht----- Von: jun...@li... = [mailto:jun...@li...] Im Auftrag von J. David = Beutel Gesendet: Sonntag, 12. M=E4rz 2006 23:47 An: jun...@li... Betreff: Re: [Junit-devel] cvs-timeout I've had the same problem, and better luck with SourceForge's anonymous=20 Subversion (so far, anyway). Also, I prefer Subversion. Cheers, 11011011 David Saff <sa...@mi...> wrote on 03/08/2006 08:37:41 AM: > Matt, > > Anonymous pserver CVS access to SourceForge is absolutely terrible. =20 > Committers get CVS/SSH access, which is reasonably fast, so the people = > to whom SourceForge is most likely to listen are least likely to=20 > complain. I actually ended up setting up a daemon that tried to=20 > update every hour, so that when I sat down to develop, there was a=20 > good chance that I had an up-to-date version. Of course, this just=20 > contributed to everyone else's traffic, so there's probably a better=20 > solution somewhere. > > Sorry, > > David Saff > > Mat...@un... wrote: >> >> Hi *.*, >> >> =20 >> >> is it just me or do you guys also get lots of timeouts when trying to = >> synchronize with the sourceforge cvs? > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting = language that extends applications into web and mobile media. Attend the live = webcast and join the prime developer group breaking into this new coding = territory! http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ Junit-devel mailing list Jun...@li... https://lists.sourceforge.net/lists/listinfo/junit-devel |
|
From: J. D. B. <jd...@ge...> - 2006-03-12 22:41:20
|
I've had the same problem, and better luck with SourceForge's anonymous Subversion (so far, anyway). Also, I prefer Subversion. Cheers, 11011011 David Saff <sa...@mi...> wrote on 03/08/2006 08:37:41 AM: > Matt, > > Anonymous pserver CVS access to SourceForge is absolutely terrible. > Committers get CVS/SSH access, which is reasonably fast, so the people > to whom SourceForge is most likely to listen are least likely to > complain. I actually ended up setting up a daemon that tried to > update every hour, so that when I sat down to develop, there was a > good chance that I had an up-to-date version. Of course, this just > contributed to everyone else's traffic, so there's probably a better > solution somewhere. > > Sorry, > > David Saff > > Mat...@un... wrote: >> >> Hi *.*, >> >> >> >> is it just me or do you guys also get lots of timeouts when trying to >> synchronize with the sourceforge cvs? > |
|
From: David S. <ds...@us...> - 2006-03-10 00:52:19
|
Update of /cvsroot/junit/junit/org/junit In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1356/org/junit Modified Files: After.java Before.java Assert.java ComparisonFailure.java AfterClass.java Log Message: Patched javadoc, thanks to Matthias Schmidt RunWith is @Inherited Added acknowledgements to-do is up to date Index: After.java =================================================================== RCS file: /cvsroot/junit/junit/org/junit/After.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- After.java 15 Feb 2006 22:55:30 -0000 1.2 +++ After.java 10 Mar 2006 00:52:15 -0000 1.3 @@ -6,10 +6,10 @@ import java.lang.annotation.Target; /** - * If you allocate external resources in a <code>@Before</code> method you need to release them + * If you allocate external resources in a {@link org.junit.Before} method you need to release them * after the test runs. Annotating a <code>public void</code> method - * with <code>@After</code> causes that method to be run after the <code>@Test</code> method. All <code>@After</code> - * methods are guaranteed to run even if a <code>@Before</code> or <code>@Test</code> method throws an + * with <code>@After</code> causes that method to be run after the {@link org.junit.Test} method. All <code>@After</code> + * methods are guaranteed to run even if a {@link org.junit.Before} or {@link org.junit.Test} method throws an * exception. The <code>@After</code> methods declared in superclasses will be run after those of the current * class. * <p> @@ -30,6 +30,7 @@ * </code> * * @see org.junit.Before + * @see org.junit.Test */ @Retention(RetentionPolicy.RUNTIME) Index: Before.java =================================================================== RCS file: /cvsroot/junit/junit/org/junit/Before.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- Before.java 15 Feb 2006 22:55:30 -0000 1.2 +++ Before.java 10 Mar 2006 00:52:15 -0000 1.3 @@ -8,7 +8,7 @@ /** * When writing tests, it is common to find that several tests need similar * objects created before they can run. Annotating a <code>public void</code> method - * with <code>@Before</code> causes that method to be run before the <code>@Test</code> method. + * with <code>@Before</code> causes that method to be run before the {@link org.junit.Test} method. * The <code>@Before</code> methods of superclasses will be run before those of the current class. * <p> * Here is a simple example: Index: Assert.java =================================================================== RCS file: /cvsroot/junit/junit/org/junit/Assert.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- Assert.java 15 Feb 2006 22:55:30 -0000 1.2 +++ Assert.java 10 Mar 2006 00:52:15 -0000 1.3 @@ -9,18 +9,23 @@ * ...<br> * assertEquals(...);<br> * </code> + * + * @see java.lang.AssertionError */ - public class Assert { /** * Protect constructor since it is a static only class */ protected Assert() { } + + // TODO: param comments should start with lower case letters /** * Asserts that a condition is true. If it isn't it throws an - * AssertionError with the given message. + * {@link AssertionError} with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param condition condition to be checked */ static public void assertTrue(String message, boolean condition) { if (!condition) @@ -29,7 +34,8 @@ /** * Asserts that a condition is true. If it isn't it throws an - * AssertionError. + * {@link AssertionError} without a message. + * @param condition condition to be checked */ static public void assertTrue(boolean condition) { assertTrue(null, condition); @@ -37,7 +43,9 @@ /** * Asserts that a condition is false. If it isn't it throws an - * AssertionError with the given message. + * {@link AssertionError} with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param condition condition to be checked */ static public void assertFalse(String message, boolean condition) { assertTrue(message, !condition); @@ -45,7 +53,8 @@ /** * Asserts that a condition is false. If it isn't it throws an - * AssertionError. + * {@link AssertionError} without a message. + * @param condition condition to be checked */ static public void assertFalse(boolean condition) { assertFalse(null, condition); @@ -53,6 +62,8 @@ /** * Fails a test with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @see AssertionError */ static public void fail(String message) { throw new AssertionError(message); @@ -67,7 +78,10 @@ /** * Asserts that two objects are equal. If they are not, an - * AssertionError is thrown with the given message. + * {@link AssertionError} is thrown with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param expected expected value + * @param actual actual value */ static public void assertEquals(String message, Object expected, Object actual) { if (expected == null && actual == null) @@ -82,7 +96,9 @@ /** * Asserts that two objects are equal. If they are not, an - * AssertionError is thrown. + * {@link AssertionError} without a message is thrown. + * @param expected expected value + * @param actual the value to check against <code>expected</code> */ static public void assertEquals(Object expected, Object actual) { assertEquals(null, expected, actual); @@ -90,7 +106,10 @@ /** * Asserts that two object arrays are equal. If they are not, an - * AssertionError is thrown with the given message. + * {@link AssertionError} is thrown with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param expecteds Object array or array of arrays (multi-dimensional array) with expected values + * @param actuals Object array or array of arrays (multi-dimensional array) with actual values */ public static void assertEquals(String message, Object[] expecteds, Object[] actuals) { if (expecteds == actuals) @@ -117,7 +136,9 @@ /** * Asserts that two object arrays are equal. If they are not, an - * AssertionError is thrown. + * {@link AssertionError} is thrown. + * @param expecteds Object array or array of arrays (multi-dimensional array) with expected values + * @param actuals Object array or array of arrays (multi-dimensional array) with actual values */ public static void assertEquals(Object[] expecteds, Object[] actuals) { assertEquals(null, expecteds, actuals); @@ -125,10 +146,15 @@ /** * Asserts that two doubles are equal to within a positive delta. If they - * are not, an AssertionError is thrown with the given message. If the + * are not, an {@link AssertionError} is thrown with the given message. If the * expected value is infinity then the delta value is ignored. NaNs are * considered equal: - * assertEquals(Double.NaN, Double.NaN, *) passes + * <code>assertEquals(Double.NaN, Double.NaN, *)</code> passes + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param expected expected value + * @param actual the value to check against <code>expected</code> + * @param delta the maximum delta between <code>expected</code> and <code>actual</code> for which + * both numbers are still considered equal. */ static public void assertEquals(String message, double expected, double actual, double delta) { if (Double.compare(expected, actual) == 0) @@ -139,10 +165,14 @@ /** * Asserts that two doubles are equal to within a positive delta. If they - * are not, an AssertionError is thrown. If the + * are not, an {@link AssertionError} is thrown. If the * expected value is infinity then the delta value is ignored.NaNs are * considered equal: - * assertEquals(Double.NaN, Double.NaN, *) passes + * <code>assertEquals(Double.NaN, Double.NaN, *)</code> passes + * @param expected expected value + * @param actual the value to check against <code>expected</code> + * @param delta the maximum delta between <code>expected</code> and <code>actual</code> for which + * both numbers are still considered equal. */ static public void assertEquals(double expected, double actual, double delta) { assertEquals(null, expected, actual, delta); @@ -150,10 +180,15 @@ /** * Asserts that two floats are equal to within a positive delta. If they - * are not, an AssertionError is thrown with the given message. If the + * are not, an {@link AssertionError} is thrown with the given message. If the * expected value is infinity then the delta value is ignored.NaNs are * considered equal: - * assertEquals(Float.NaN, Float.NaN, *) passes + * <code>assertEquals(Float.NaN, Float.NaN, *)</code> passes + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param expected the expected float value + * @param actual the float value to check against <code>expected</code> + * @param delta the maximum delta between <code>expected</code> and <code>actual</code> for which + * both numbers are still considered equal. */ static public void assertEquals(String message, float expected, float actual, float delta) { if (Float.compare(expected, actual) == 0) @@ -164,42 +199,52 @@ /** * Asserts that two floats are equal to within a positive delta. If they - * are not, an AssertionError is thrown. If the - * expected value is infinity then the delta value is ignored.NaNs are + * are not, an {@link AssertionError} is thrown. If the + * expected value is infinity then the delta value is ignored. {@link Float#NaN NaNs} are * considered equal: - * assertEquals(Float.NaN, Float.NaN, *) passes + * <code>assertEquals(Float.NaN, Float.NaN, *)</code> passes + * @param expected the expected value + * @param actual the value to check against <code>expected</code> + * @param delta the maximum delta between <code>expected</code> and <code>actual</code> for which + * both numbers are still considered equal. */ static public void assertEquals(float expected, float actual, float delta) { assertEquals(null, expected, actual, delta); } /** - * Asserts that an object isn't null. If it is an AssertionError is + * Asserts that an object isn't null. If it is an {@link AssertionError} is * thrown with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param object Object to check or <code>null</code> */ static public void assertNotNull(String message, Object object) { assertTrue(message, object != null); } /** - * Asserts that an object isn't null. If it is an AssertionError is + * Asserts that an object isn't null. If it is an {@link AssertionError} is * thrown. + * @param object Object to check or <code>null</code> */ static public void assertNotNull(Object object) { assertNotNull(null, object); } /** - * Asserts that an object is null. If it is not, an AssertionError is + * Asserts that an object is null. If it is not, an {@link AssertionError} is * thrown with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param object Object to check or <code>null</code> */ static public void assertNull(String message, Object object) { assertTrue(message, object == null); } /** - * Asserts that an object is null. If it isn't an AssertionError is + * Asserts that an object is null. If it isn't an {@link AssertionError} is * thrown. + * @param object Object to check or <code>null</code> */ static public void assertNull(Object object) { assertNull(null, object); @@ -207,7 +252,10 @@ /** * Asserts that two objects refer to the same object. If they are not, an - * AssertionError is thrown with the given message. + * {@link AssertionError} is thrown with the given message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param expected the expected object + * @param actual the object to compare to <code>expected</code> */ static public void assertSame(String message, Object expected, Object actual) { if (expected == actual) @@ -217,7 +265,9 @@ /** * Asserts that two objects refer to the same object. If they are not the - * same, an AssertionError is thrown. + * same, an {@link AssertionError} without a message is thrown. + * @param expected the expected object + * @param actual the object to compare to <code>expected</code> */ static public void assertSame(Object expected, Object actual) { assertSame(null, expected, actual); @@ -225,20 +275,25 @@ /** * Asserts that two objects do not refer to the same object. If they do - * refer to the same object, an AssertionError is thrown with the given + * refer to the same object, an {@link AssertionError} is thrown with the given * message. + * @param message the identifying message or <code>null</code> for the {@link AssertionError} + * @param unexpected the object you don't expect + * @param actual the object to compare to <code>unexpected</code> */ - static public void assertNotSame(String message, Object expected, Object actual) { - if (expected == actual) + static public void assertNotSame(String message, Object unexpected, Object actual) { + if (unexpected == actual) failSame(message); } /** * Asserts that two objects do not refer to the same object. If they do - * refer to the same object, an AssertionError is thrown. + * refer to the same object, an {@link AssertionError} without a message is thrown. + * @param unexpected the object you don't expect + * @param actual the object to compare to <code>unexpected</code> */ - static public void assertNotSame(Object expected, Object actual) { - assertNotSame(null, expected, actual); + static public void assertNotSame(Object unexpected, Object actual) { + assertNotSame(null, unexpected, actual); } static private void failSame(String message) { Index: ComparisonFailure.java =================================================================== RCS file: /cvsroot/junit/junit/org/junit/ComparisonFailure.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- ComparisonFailure.java 15 Feb 2006 22:55:30 -0000 1.2 +++ ComparisonFailure.java 10 Mar 2006 00:52:15 -0000 1.3 @@ -1,7 +1,7 @@ package org.junit; /** - * Thrown when an assertEquals(String, String) fails. Create and throw + * Thrown when an {@link org.junit.Assert#assertEquals(Object, Object) assertEquals(String, String)} fails. Create and throw * a <code>ComparisonFailure</code> manually if you want to show users the difference between two complex * strings. * @@ -38,14 +38,14 @@ } /** - * Returns the actual value + * Returns the actual string value * @return the actual string value */ public String getActual() { return fActual; } /** - * Returns the expected value + * Returns the expected string value * @return the expected string value */ public String getExpected() { Index: AfterClass.java =================================================================== RCS file: /cvsroot/junit/junit/org/junit/AfterClass.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- AfterClass.java 15 Feb 2006 22:55:30 -0000 1.2 +++ AfterClass.java 10 Mar 2006 00:52:15 -0000 1.3 @@ -6,10 +6,10 @@ import java.lang.annotation.Target; /** - * If you allocate expensive external resources in a <code>@BeforeClass</code> method you need to release them + * If you allocate expensive external resources in a {@link org.junit.BeforeClass} method you need to release them * after all the tests in the class have run. Annotating a <code>public static void</code> method * with <code>@AfterClass</code> causes that method to be run after all the tests in the class have been run. All <code>@AfterClass</code> - * methods are guaranteed to run even if a <code>@BeforeClass</code> method throws an + * methods are guaranteed to run even if a {@link org.junit.BeforeClass} method throws an * exception. The <code>@AfterClass</code> methods declared in superclasses will be run after those of the current * class. * <p> @@ -33,6 +33,7 @@ * </code> * * @see org.junit.BeforeClass + * @see org.junit.Test */ @Retention(RetentionPolicy.RUNTIME) |
|
From: David S. <ds...@us...> - 2006-03-10 00:52:19
|
Update of /cvsroot/junit/junit/junit/runner In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1356/junit/runner Modified Files: Version.java Log Message: Patched javadoc, thanks to Matthias Schmidt RunWith is @Inherited Added acknowledgements to-do is up to date Index: Version.java =================================================================== RCS file: /cvsroot/junit/junit/junit/runner/Version.java,v retrieving revision 1.15 retrieving revision 1.16 diff -u -d -r1.15 -r1.16 --- Version.java 8 Mar 2006 21:22:53 -0000 1.15 +++ Version.java 10 Mar 2006 00:52:15 -0000 1.16 @@ -9,7 +9,7 @@ } public static String id() { - return "4.0"; + return "4.1"; } public static void main(String[] args) { |
|
From: David S. <ds...@us...> - 2006-03-10 00:52:19
|
Update of /cvsroot/junit/junit In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1356 Modified Files: build.xml done.txt to-do.txt Added Files: acknowledgements.txt Log Message: Patched javadoc, thanks to Matthias Schmidt RunWith is @Inherited Added acknowledgements to-do is up to date --- NEW FILE: acknowledgements.txt --- 2006 March 9 Matthias Schmidt: improved org.junit package javadoc Index: build.xml =================================================================== RCS file: /cvsroot/junit/junit/build.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -d -r1.15 -r1.16 --- build.xml 27 Feb 2006 19:01:37 -0000 1.15 +++ build.xml 10 Mar 2006 00:52:15 -0000 1.16 @@ -1,6 +1,6 @@ <project name="junit" default="dist" basedir="."> <property file="${user.home}/.junit.properties" /> - <property name="version" value="4.0" /> + <property name="version" value="4.1" /> <property name="dist" value="junit${version}" /> <property name="versionfile" value="junit/runner/Version.java" /> <property name="zipfile" value="${dist}.zip" /> Index: done.txt =================================================================== RCS file: /cvsroot/junit/junit/done.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- done.txt 15 Feb 2006 22:55:27 -0000 1.2 +++ done.txt 10 Mar 2006 00:52:15 -0000 1.3 @@ -39,5 +39,12 @@ * make sure TestListener is symmetric and meets needs of runner developers * TestRunEvent * Decide how we ship JUnit-- 1.5 only or hybrid - + * README.html +* add javadoc to API interfaces and Annotations + http://java.sun.com/j2se/javadoc/writingapispecs/index.html +* Merge branch back into head +* review Ant scripts +* make suites simpler for both the IDE providers and the users +* ClassRequest should search up the hierarchy for the requested Class to look for @RunWith + \ No newline at end of file Index: to-do.txt =================================================================== RCS file: /cvsroot/junit/junit/to-do.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- to-do.txt 15 Feb 2006 22:55:28 -0000 1.2 +++ to-do.txt 10 Mar 2006 00:52:15 -0000 1.3 @@ -1,26 +1,18 @@ -Before first public release: * update documentation * new cook's tour * update Test Infected - * README.html -* add javadoc to API interfaces and Annotations - http://java.sun.com/j2se/javadoc/writingapispecs/index.html -* review Ant scripts -* Merge branch back into head -* ClassRequest should search up the hierarchy for the requested Class to look for @RunWith * Should there be a "prefix" annotation for Suites? * This would allow two Suites with different BeforeClass/AfterClass behaviors, but the same component tests, to co-exist -Before next JUnit 4 release: * update the build process * automatically upload a new JAR * update site for plug-in version? -* make suites simpler for both the IDE providers and the users -* class level test annotations? * Ant * Basic task * support testing run once initialization code e.g. class Foo {{...}} * Automatically add failing tests to the Known Defects section of the README.html - +* Create test target in ant +* Organize org.junit.tests +* Use <pre></pre> for javadoc code examples \ No newline at end of file |
|
From: David S. <ds...@us...> - 2006-03-10 00:52:19
|
Update of /cvsroot/junit/junit/org/junit/tests In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1356/org/junit/tests Modified Files: RunWithTest.java Log Message: Patched javadoc, thanks to Matthias Schmidt RunWith is @Inherited Added acknowledgements to-do is up to date Index: RunWithTest.java =================================================================== RCS file: /cvsroot/junit/junit/org/junit/tests/RunWithTest.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- RunWithTest.java 15 Feb 2006 22:55:29 -0000 1.2 +++ RunWithTest.java 10 Mar 2006 00:52:15 -0000 1.3 @@ -48,6 +48,17 @@ assertTrue(log.contains("initialize")); assertTrue(log.contains("run")); } + + public static class SubExampleTest extends ExampleTest { + } + + @Test public void runWithExtendsToSubclasses() { + log= ""; + + JUnitCore.runClasses(SubExampleTest.class); + assertTrue(log.contains("run")); + } + public static junit.framework.Test suite() { return new JUnit4TestAdapter(RunWithTest.class); |
37 messages has been excluded from this view by a project administrator.
