Bug 559125 - [JUnit] Support running multiple selected test files
Summary: [JUnit] Support running multiple selected test files
Status: CLOSED DUPLICATE of bug 29658
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.14   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-13 14:19 EST by Pierre-Yves Bigourdan CLA
Modified: 2020-01-14 02:22 EST (History)
1 user (show)

See Also:

Attachments
Cannot run tests for multi select (130.42 KB, image/png)
2020-01-13 14:19 EST, Pierre-Yves Bigourdan CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Yves Bigourdan CLA 2020-01-13 14:19:26 EST 
Created attachment 281476 [details]
Cannot run tests for multi select

Eclipse currently supports running JUnit contained in a single file, package, project, etc. However, when selecting multiple test files in the Package/Project Explorer, there is no option to run these files as JUnit tests (see attached screenshot).

When working on a small project, you can either run test files one by one or run the whole package, but on much bigger projects these workarounds become unpractical.
Comment 1 Noopur Gupta CLA 2020-01-14 00:33:03 EST 
Similar to bug 111126.

*** This bug has been marked as a duplicate of bug 111126 ***
Comment 2 Pierre-Yves Bigourdan CLA 2020-01-14 02:12:22 EST 
(In reply to Noopur Gupta from comment #1)
> Similar to bug 111126.
> 
> *** This bug has been marked as a duplicate of bug 111126 ***

Not convinced it's a duplicate. That bug is about running multiple projects at a time, which has challenges mainly around handling different classpaths for each project.

Here the use case is fairly different: rather than running everything in multiple projects, I'm requesting to be able to run a subset within a single project. The classpath problem does not apply here and I suspect the implementation would potentially look quite different - as well as probably simpler.
Comment 3 Noopur Gupta CLA 2020-01-14 02:22:09 EST 
bug 29658 would be the right duplicate.

*** This bug has been marked as a duplicate of bug 29658 ***