Summary: | [JUnit] Remember superclass in JUnit Test Case wizard | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | J. B. Rainsberger <jbr> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P4 | CC: | preuss |
Version: | 3.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
J. B. Rainsberger
2005-10-29 13:15:51 EDT
Ditto here! What we could do is to use the current selection if it extends TestCase. Is that good enough? The problem of initializing a field is always that it is also nasty for the user when its wrong. (In reply to comment #2) > What we could do is to use the current selection if it extends TestCase. Is > that good enough? > The problem of initializing a field is always that it is also nasty for the > user when its wrong. At work, we have our own root TestCase class that adds a number of commonly used assert methods. We want to use that one in 99% of all cases. So, no, for us using the current selection wouldn't work - initializing the field with a value defined once is exactly what we want. What would also work is if the field remembered its last value, perhaps even with a history. (This might become less relevant with JUnit 4, I guess...) |