Menu
▾
▴
[Junit-devel] Re: Junit-devel digest, Vol 1 #345 - 4 msgs
|
From: Trasca V. <vir...@ya...> - 2006-03-17 19:26:49
|
Hi Matthias,
Thanks for your answer. I was thinking to your aproach
with
public static void testAll( ) {
myTestM1( );
myTestM2( );
}
The problem that I feel with this aproach is that I
will get testAll failed. I will not know exactly what
method failed. And for what I want to do this could be
a big problem.
I have a very big EJB API(hundreds of classes) for
which I want to make some kind of automated regression
testing. Using AspectJ I want to profile/serialize all
public method calls with param/output value when I am
walking throug the application GUI. After that I want
to generate automatically(from the xml with method
calls)a big test case JUnit class which will call
all the method that were recorded, give the recorded
params and to check that the return values are the
same as there were initial recorded. Problem is that I
will have hundred of method calls which are
dependentely 1 for each one(maybe method 1 puts the
bean in a special state that method 2 needs).
In the final I think I will take your aproach but
there are some disadvantages.
Thanks,
Virgil
--- jun...@li... wrote:
> Send Junit-devel mailing list submissions to
> jun...@li...
>
> To subscribe or unsubscribe via the World Wide Web,
> visit
>
>
https://lists.sourceforge.net/lists/listinfo/junit-devel
> or, via email, send a message with subject or body
> 'help' to
> jun...@li...
>
> You can reach the person managing the list at
> jun...@li...
>
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of Junit-devel digest..."
>
>
> Today's Topics:
>
> 1. AW: [Junit-devel] SourceForge CVS
> (Mat...@un...)
> 2. Re: AW: [Junit-devel] SourceForge CVS (David
> Saff)
> 3. Order in which test methods are run in a
> testcase (Trasca Virgil)
> 4. Re: Order in which test methods are run in a
> testcase (Matthias Schmidt)
>
> --__--__--
>
> Message: 1
> Subject: AW: [Junit-devel] SourceForge CVS
> Date: Fri, 17 Mar 2006 09:52:02 +0100
> From: <Mat...@un...>
> To: <jun...@li...>
>
> Still no change, is there? I haven't been able to
> synchronize with cvs =
> since sunday ....
>
> ________________________________
>
> Von: jun...@li... im
> Auftrag von David Saff
> Gesendet: Do 16.03.2006 19:21
> An: JUnit devel
> Betreff: [Junit-devel] SourceForge CVS
>
>
>
> All,
>
> I've heard back from SourceForge. Some quotes from
> below:
>
> >>>>>>
>
> Per the site status page:
>
> ( 2006-03-13 12:42:16 - Project CVS Service ) As
> of
> 2006-03-12 pserver (anonymous) CVS services, along
> with
> tarballs and ViewCVS are down for projects that
> start with
> the letters e, i, j, o, v, w and x. We hope to
> resolve this
> issue in the next 2 days.
>
> Please keep an eye there for further updates to this
> issue.
>
> [snip]
>
> However, the CVS issues we have been having are
> generally
> hardware related. We are working on swapping out the
> hardware and attempting to isolate the causes, but
> this
> takes time to do, and given the infrastructure and
> volume of
> use, we'd prefer to keep it up, even if only
> limping, than
> take it down for a complete overhaul.
>
> <<<<<<
>
> It looks like our options are to sit and wait, or
> change the name of the
> project to UnitJ. No guarantees were made about
> subversion speed, so if
> we decided to change to SVN, it would not
> necessarily be for long-term
> reliability. Thanks,
>
> David Saff
>
> -------- Original Message --------
> Subject: [ alexandria-Support
> Requests-1450494 ] CVS services =
> issue
> Date: Thu, 16 Mar 2006 06:28:55 -0800
> From: SourceForge.net <no...@so...>
> To: no...@so...
>
>
>
> Support Requests item #1450494, was opened at
> 2006-03-15 11:14
> Message generated for change (Comment added) made by
> burley
> You can respond by visiting:
>
https://sourceforge.net/tracker/?func=3Ddetail&atid=3D200001&aid=3D145049=
> 4&group_id=3D1
>
> Please note that this message will contain a full
> copy of the comment =
> thread,
> including the initial issue submission, for this
> request,
> not just the latest update.
> Category: Project CVS Services
> Group: None
> >Status: Closed
> Priority: 5
> Submitted By: David Saff (dsaff)
> >Assigned to: David Burley (burley)
> >Summary: CVS services issue
>
> Initial Comment:
> Dear SourceForge,
>
> Over the last few months, public anonymous access to
> JUnit CVS has become so slow and unreliable that it
> has
> slowed the pace at which we are able to accept
> patches
> and support early adopters. Is there anything we or
> you can do to solve this problem? Are the
> subversion
> servers faster? Will the subversion servers stay
> fast
> if many people switch over?
>
> Below is a sampling of independent mailing list
> messages indicating the kinds of problems seen.
> Thanks,
>
> David Saff
>
> 2006/03/15: "I attempted to check out the current
> CVS
> HEAD, but the system was unresponsive."
>
> 2006/03/14: "I will send Javadoc updates for the
> classes as soon as cvs.sourceforge.net stops timing
> out
> :-(. It usually works when America is asleep (in the
> morning over here) ...."
>
> 2006/03/08: "is it just me or do you guys also get
> lots
> of timeouts when trying to synchronize with the
> sourceforge cvs?"
>
> 2005/10/24: "I have found the SourceForge CVS server
> _extremely_ sluggish and unreliable."
>
> 2005/09/14: "I get varying errors depending on the
> client,
> but they seem to all be related to
> either the CVS server timing out or the connection
> being refused."
>
>
----------------------------------------------------------------------
>
> >Comment By: David Burley (burley)
> Date: 2006-03-16 09:28
>
> Message:
> Logged In: YES
> user_id=3D597273
>
> Greetings,
>
> Per the site status page:
>
> ( 2006-03-13 12:42:16 - Project CVS Service ) As
> of
> 2006-03-12 pserver (anonymous) CVS services, along
> with
> tarballs and ViewCVS are down for projects that
> start with
> the letters e, i, j, o, v, w and x. We hope to
> resolve this
> issue in the next 2 days.
>
> Please keep an eye there for further updates to this
> issue.
>
=== message truncated ===
|
