https://bugs.documentfoundation.org/show_bug.cgi?id=128329
--- Comment #10 from Buovjaga <[email protected]> ---
(In reply to b. from comment #9)
> for better forensics ... what about implementing an activity protocol and a
> re-roll functionality, once somebody spottes an error he can save the file
> with it's original values, and a 'script' about his actions, then that
> script can be rolled through step by step, if the error shows up you have
> 'steps', if not you have clue about 'weak hardware' or a sporadic fail in
> software ...
Well, we have a logger which can even automatically create UI tests:
https://ahmedelshreif.blogspot.com/2019/08/gsoc-final-report.html
https://ahmedelshreifgsoc20.blogspot.com/2020/08/gsoc20-final-report-project.html
https://www.youtube.com/watch?v=nnng_er2mro
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
