| Summary: | Launch several testcase with JUnit [JUnit] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Giannandrea Castaldi <g.castal> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | Keywords: | helpwanted |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Giannandrea Castaldi
We should add multiple test case support for a JUnit launch configuraiton. However, this currently has lower priority. To have the chance of executing only a part of my tests in accordance with the environment that I'm running our system on (development, integration, production) I would like a solution like these: 1. I introduce in my project some empty interface (Development, Integration, Production for example) that I use as tags to classify my test 2. Than in "JUnit Test Finder" I can configure the interfaces to use for selecting the test 3. From "JUnit Test Finder" I can run only the tests that implements one of these interface have to defer No action planed for 2.1. Tagged as help wanted in the 2.1 stream there is now support to run all tests inside a package, source folder, or projects. Chaning state from assigned later to resolved later. Assigned later got introduced by the last bug conversion and is not a supported Eclipse bug state. This is a useful feature request, and it is still not resolved in Eclipse 3.1. The first thing which comes to my mind to control test selection is an exclude list. Also it worth to have some keyword-based mechanism based on javadoc or java 5.0 annotations - using interfaces for test markup look a bit heavy for me. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |