Bugzilla – Full Text Bug Listing
| Summary: | UI creates bad run configuration for individual tests | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | David Bustos <david> |
| Component: | UI | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.7.1a | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
Moving to UI This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
When I right-click on a test method and try to run it as a JUnit test, it fails immediately with "initializationError". The run configuration includes the arguments, like "testPublish(io.vertx.ext.unit.TestContext)". If I remove the arguments ("testPublish"), then running the run configuration works. Right-clicking to run again creates a new run configuration, though.