Mantis Bug Tracker

View Revisions: Issue #803 All Revisions ] Back to Issue ]
Summary 0000803: Ability to "dump" steps taken by GUI when we reach a buggy state
Revision 2018-09-11 13:27 by ttsiodras
Steps To Reproduce As more and more users use TASTE and the GUI to create increasingly more complex designs, being able to report how exactly the GUI reached a bad state is very important. As-is, when this happens, it is very difficult to reliably reproduce the bad state again - but if we had the ability to "dump the steps" that were taken since the GUI was launched on this particular design, then Ellidiss would be able to consistently and reliably reproduce the issues. Such a history of "steps" should in fact already be there, since the "Undo" functionality is in all likelihood depending on something similar. We therefore ask for some way to trigger a "dump history" functionality on the GUI, that would be used anytime we need to report a GUI bug. The dumped history should contain information that describes fully the steps that drove the GUI to the "bad" state being reported - so it must be minimal and complete. Note that in contrast to the "Undo" information, this list should never have things removed from it - only appended to it (since the "Undo" operations themselves may introduce bugs).
Revision 2018-09-11 13:26 by ttsiodras
Steps To Reproduce As more and more users use TASTE and the GUI to create increasingly more complex designs, being able to report how exactly the GUI reached a bad state is very important. As-is, when this happens, it is very difficult to reliably reproduce the bad state again - but if we had the ability to "dump the steps" that were taken since the GUI was launched on this particular design, then Ellidiss would be able to consistently and reliably reproduce the issues. Such a history of "steps" should in fact already be there, since the "Undo" functionality is in all likelihood depending on something similar. We therefore ask for some way to trigger a "dump history" functionality on the GUI, that would be used anytime we need to report a GUI bug. The dumped history should contain information that is irrelevant to TASTE users, but must describe fully the steps that drove the GUI to the "bad" state being reported - so it must be minimal and complete. Note that in contrast to the "Undo" information, this list should never have things removed from it - only appended to it (since the "Undo" operations themselves may introduce bugs).
Revision 2018-09-11 13:23 by ttsiodras
Steps To Reproduce As more and more users use TASTE and the GUI to create increasingly more complex designs, being able to report how exactly the GUI reached a bad state is very important. As-is, when this happens, it is very difficult to reliably reproduce the bad state again - but if we had the ability to "dump the steps" that were taken since the GUI was launched on this particular design, then Ellidiss would be able to consistently and reliably reproduce the issues. Such a history of "steps" should in fact already be there, since the "Undo" functionality is in all likelihood depending on something similar. We therefore ask for some way to trigger a "dump history" functionality on the GUI, that would be used anytime we need to report a GUI bug.


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker