Timeline for Bugs keep reappearing in our GUI software during development. How should this be addressed?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2011 at 21:33 | history | edited | user246 | CC BY-SA 3.0 |
typo
|
| Jun 16, 2011 at 16:21 | comment | added | TristaanOgre | +1 for referencing the developers needing to test their work. GUI components and objects shouldn't be that difficult to work with so the fact that their rendering and such are breaking on almost a build to build basis indicates that the developers aren't even exercising their code on a high level. | |
| Jun 16, 2011 at 14:07 | history | edited | user246 | CC BY-SA 3.0 |
deleted 40 characters in body
|
| Jun 16, 2011 at 12:46 | comment | added | MichaelF | I'd agree with the test plan portion of this answer, if you have areas that continually regress you need a checklist, or plan, to make sure certain areas are ALWAY covered regardless. Whether this is automated, but might be hard if you have continual changes, or a checklist that can be used by Devs to check after they make changes you need something structured. I do the same when I have code that is continually changing, and also continually has issues. | |
| Jun 16, 2011 at 12:30 | history | answered | user246 | CC BY-SA 3.0 |