| Summary: | TestCase editor should be a table | ||
|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Felix Ziesel <Felix.Ziesel> |
| Component: | UI | Assignee: | Project Inbox <jubula.ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | Oliver Goetz <Oliver.Goetz> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | alexandra.schladebeck |
| Version: | unspecified | ||
| Target Milestone: | Indigo SR2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Felix Ziesel
We're rejecting this on the following grounds: - Yes, we do need to make some changes to improve the usability of writing tests, but having more information shown in one place isn't the way to do it. - Having all this information in the Test Case Editor could mean that we are getting too close to actually writing program code to write the tests - something we want to stay away from. See previous comment. |