Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


I've made some UI tests that open every dialog in calc, close it with
the "close" or "cancel" button and if there is an "OK" button open it
again and click the "OK" button

These tests should simply make sure there are no crashes by
opening/closing the dialogues and protect against regressions like
https://bugs.documentfoundation.org/show_bug.cgi?id=120227
https://bugs.documentfoundation.org/show_bug.cgi?id=125982
https://bugs.documentfoundation.org/show_bug.cgi?id=125985

I just wanted to have some feedback if picking those low-hanging fruits
is a valid approach and worth the effort and CI time.

If yes I could extend the tests by:

 1. doing the same for writer, impress, etc.
 2. delete obsolete tests like uitest/calc_tests/about_test.py
 3. define preconditions for the "OK" click, e.g. input data into fields
 4. define assertion after the click on the "OK" button

Thoughts? Ideas?

-- 
Artur Neumann
Director/CTO
Jankari Tech Pvt Ltd
www.jankaritech.com
Phone: +977 9806639223
Skype: artur.n.
GitHub: https://github.com/individual-it


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.