1) "go to test" is nice but "toggle between test and class" would be even more 
powerful IMHO. Idealy the same command would do "go to test" and "go to class under 
test" based on which class I am in currently.
I know I can do that with back/forward or next/previous tab once I have used the "go 
to test" but I might look at something else in between and that would add classes to 
my navigation history or my opened tab.

2) Taking the "test class"/"class under test" relationship to the next level we could 
have 1 tab for the pair with a toggle class/test or a resizable split view for them (1 
test split and 1 class split). That way you can decrease the number of tabs. With the 
split view I can really work on the test and the class under test at the same time 
without context switching.

3) To generalize 1) we could define relationship between files through naming patterns 
and class semantics (extends from a certain base class) and have customizable 
navigation shortcuts. That way you can speed up your frameworks navigation 
tremendously:
The EJB framework is a good example: 
bean -> remote interface -> interface -> home -> ejb-jar = a navigation toggle could 
be implemented that would cycle through or navigation directly to 1 EJB related files. 
Potential create them if they do not exist based on a template.
The Junit testclass -> class relationship is just one application of this generic 
principle for the junit framework.

-----Original Message-----
From: Vollmer, Thomas - CannonSA [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 29, 2002 11:59 AM
To: [EMAIL PROTECTED]
Subject: RE: Create TestCase (Was: RE: [Eap-features] Make a union of
packages in various source tre es ...)


+1 for "go to test".
+1 for "create test from class".

It would be nice if the naming scheme 
and template for the new tests would
be configurable.

-Thomas

> -----Original Message-----
> From: Per Mellqvist [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 29, 2002 9:24 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Create TestCase (Was: RE: [Eap-features] Make a union of
> packages in various source tre es ...)
> 
> 
> +1
> 
> If the test-source directory was configurable in the project 
> properties
> there could also be a
> "Go to test" option when right clicking a class that has a test with a
> corresponding name.
> 
> // Per Mellqvist
> 
> ----- Original Message -----
> From: "Thomas Singer" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 29, 2002 10:17 AM
> Subject: Create TestCase (Was: RE: [Eap-features] Make a 
> union of packages
> in various source tre es ...)
> 
> 
> We have our Unit-Test in a separate folder structure, too. 
> Therefor I would
> like to request a new IDEA feature that helps me to create 
> the tests. One
> possibility could be:
> 
> - right click on a class (e.g. QStringUtils), choose "Create 
> TestCase ...",
> - IDEA asks me for the target-directory (the mounted root 
> directory - not
> the package) and
> - IDEA creates a new class in the same package but in the specified
> directory and names it useful (e.g. QStringUtilsTest)
> 
> The created test case should already be derived from TestCase 
> and should
> have the constructor. If the package does not exists in the
> target-directory, it should be autogenerated.
> 
> Best regards,
> Thomas Singer
> 
> >I can see the merits of a combined view but please make it optional,
> >as Michael suggests. We have unit tests in the same package as the
> >class but they're in a separate folder structure. I find this very
> >helpful and like IDEA's way of displaying them separately.
> >
> >Regards.
> >-Thomas
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Michael Descher [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, January 24, 2002 12:38 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: AW: [Eap-features] Make a union of packages in 
> various source
> > > trees ...
> > >
> > >
> > > Usually I don't care about where a source file really is
> > > because I'm using
> > > CTRL+N to open them in a second (opposed to browsing package
> > > structures in
> > > JBuilder looking for class files and not finding them). The
> > > improvements on
> > > this feature in the next version will make it even better I
> > > think (e.g.
> > > opening other files the same way).
> > >
> > > The idea of combining source paths is a nice options of 
> course and you
> > > should be able to switch between the two (current and 
> combined) views
> > > easily.
> > >
> > > Michael
> > >
> > > > -----Urspr�ngliche Nachricht-----
> > > > Von: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]Im Auftrag von
> > > > [EMAIL PROTECTED]
> > > > Gesendet: Donnerstag, 24. Januar 2002 20:49
> > > > An: [EMAIL PROTECTED]
> > > > Betreff: RE: [Eap-features] Make a union of packages in
> > > various source
> > > > trees ...
> > > >
> > > >
> > > > +10
> > > >
> > > > this has been mentioned by me and others in the past. 
> And presently
> > > > because of this I have little purpose for the source and
> > > classpath views
> > > > in IDEA because they don't really offer a different view of
> > > the project
> > > > than does the project.
> > > >
> > > > Florian Hehlen
> > > >
> > > > -----Original Message-----
> > > > From: rdifalco
> > > > Sent: 24 January 2002 20:36
> > > > To: eap-features
> > > > Cc: rdifalco
> > > > Subject: [Eap-features] Make a union of packages in 
> various source
> > > > trees...
> > > >
> > > >
> > > > It would be AWESOME if in either the Project or Source view
> > > you could
> > > > combine the packages from your various source directories
> > > into a single
> > > > package tree.
> > > >
> > > > For example, with have different vobs for our product line
> > > architecture.
> > > > Something like com.tripwire.space.products may be in one
> > > source path and
> > > > com.tripwire.space.core might be in another. Personally, I
> > > don't care
> > > > about
> > > > seeing the paths and would just like to see a single 
> package tree to
> > > > navigate source with. I believe JBuilder works this way.
> > > So, far, this
> > > > is my
> > > > biggest complaint.
> > > >
> > > > R.
> > > >
> > > > _______________________________________________
> > > > Eap-features mailing list
> > > > [EMAIL PROTECTED]
> > > > http://www.intellij.com/mailman/listinfo/eap-features
> > > >
> > > >
> > > >
> > > > Visit our website at http://www.ubswarburg.com
> > > >
> > > > This message contains confidential information and is 
> intended only
> > > > for the individual named.  If you are not the named 
> addressee you
> > > > should not disseminate, distribute or copy this e-mail.  Please
> > > > notify the sender immediately by e-mail if you have 
> received this
> > > > e-mail by mistake and delete this e-mail from your system.
> > > >
> > > > E-mail transmission cannot be guaranteed to be secure 
> or error-free
> > > > as information could be intercepted, corrupted, lost, destroyed,
> > > > arrive late or incomplete, or contain viruses.  The 
> sender therefore
> > > > does not accept liability for any errors or omissions in
> > > the contents
> > > > of this message which arise as a result of e-mail 
> transmission.  If
> > > > verification is required please request a hard-copy 
> version.  This
> > > > message is provided for informational purposes and should not be
> > > > construed as a solicitation or offer to buy or sell any
> > > securities or
> > > > related financial instruments.
> > > >
> > > >
> > > > _______________________________________________
> > > > Eap-features mailing list
> > > > [EMAIL PROTECTED]
> > > > http://www.intellij.com/mailman/listinfo/eap-features
> > > >
> > >
> > >
> > > _______________________________________________
> > > Eap-features mailing list
> > > [EMAIL PROTECTED]
> > > http://www.intellij.com/mailman/listinfo/eap-features
> > >
> >
> >************************************
> >If this email is not intended for you, or you are not 
> responsible for the
> >delivery of this message to the addressee, please note that 
> this message
> may
> >contain ITT Privileged/Proprietary Information.  In such a 
> case, you may
> not
> >copy or deliver this message to anyone.  You should destroy 
> this message
> and
> >kindly notify the sender by reply email.  Information 
> contained in this
> >message that does not relate to the business of ITT is 
> neither endorsed by
> >nor attributable to ITT.
> >************************************
> >
> >
> >_______________________________________________
> >Eap-features mailing list
> >[EMAIL PROTECTED]
> >http://www.intellij.com/mailman/listinfo/eap-features
> 
> 
> _______________________________________________
> Eap-features mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-features
> 
> 
> _______________________________________________
> Eap-features mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-features
> 

************************************ 
If this email is not intended for you, or you are not responsible for the
delivery of this message to the addressee, please note that this message may
contain ITT Privileged/Proprietary Information.  In such a case, you may not
copy or deliver this message to anyone.  You should destroy this message and
kindly notify the sender by reply email.  Information contained in this
message that does not relate to the business of ITT is neither endorsed by
nor attributable to ITT. 
************************************ 


_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features




_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features

Reply via email to