> 1) The difference between "test" and "run" is unclear (if there even is a > difference)
There is a difference. When you invoke "Run" (or "Debug") it creates a new run configuration and makes it "active". So when you next time invoke "Run" or "Debug" from the main menu or toolbar it runs this configuration. It's sometimes not convenient when you only need to run a particular test case without changing you default running target. I agree that the difference is very unclear but how to make it more clear? > 2) There are no options for running and/or debugging the entire test, > unless I right-click somewhere outside of a method. > > I like the new ability to run a single test, but I'd to have the option of > running the entire test case also. Yes, the only why to run the entire test case is to click somewhere outside any test method. It might be not convenient sometimes. However adding more menu items for running the entire test does not seem to be a good alternative (there are already too many items). Any ideas? -- Valentin Kipiatkov JetBrains, Inc http://www.intellij.com "Develop with pleasure!" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > If I have a JUnit test class, and I right-click in the source code window, > I'm presented with three options for running: test the current method, run > the current method and debug the current method. > > There are two issues: > 1) The difference between "test" and "run" is unclear (if there even is a > difference) > 2) There are no options for running and/or debugging the entire test, > unless I right-click somewhere outside of a method. > > I like the new ability to run a single test, but I'd to have the option of > running the entire test case also. > > > Thanks, > Galt Johnson > > _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
