The new structured manual testing instance at https://manual-test.libreoffice.org suffers again from the problem that many of the manual tests could easily be automated tests.
Since the 5.3 and even more since the 5.4 release we have an automated UI testing framework that allows us to handle even more as automated tests.
This task is about converting existing manual tests to automated UI tests.
The UI testing framework can be found at https://cgit.freedesktop.org/libreoffice/core/tree/uitest with some additional tests being at https://cgit.freedesktop.org/libreoffice/core/tree/sc/qa/uitest
https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/uitest/execute.sh contains a script that allows executing UI tests outside of the test framework with the UI visible. It helps to add time.sleep into the test to see the state after specific actions.
https://mmohrhard.wordpress.com/2016/10/03/libreoffice-ui-test-tutorial-part-1-adding-a-simple-test/ contains a short introduction into writing UI tests.
Depending on the manual test you'll find a number of items that are currently not possible to do with the UI testing framework. Please list them here and push the incomplete test to gerrit and I will try to add the support for missing pieces on the LibreOffice side.
List of .uno commands: https://wiki.documentfoundation.org/Development/DispatchCommands
Even better: by setting LO_COLLECT_UIINFO="log.txt" in the terminal you get a log with many UI actions including the uno commands in instdir/uitest.
At least the following tests should not be converted to UI tests:
EN-5:Array formula that references a cell
EN-7:Named range robustness
EN-9:Recalculation of grouped formulas
These need to be converted to automated tests in sc's ucalc.
There has been some confusion on how to get an account at TestLink. Currently the way is to register at our transitory single sign-on site: https://user.documentfoundation.org/
As the site is transitory, expect this to change in the future.
Saurav Chirania committed a patch related to this issue.
It has been pushed to "master":
tdf#107501 automatize EN-8 manual test, related tdf#84810
It will be available in 6.1.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
I was not able to use the given execute.sh script.
Since there is no file named python in my instdir/program directory, I got the following error:
I also tried modifying the command to use the python compiler I got pre-installed in my Ubuntu 16.04, but I got an ImportError:
Have I done something wrong? Please help me.
(In reply to Saurav Chirania from comment #6)
> I was not able to use the given execute.sh script.
> Since there is no file named python in my instdir/program directory, I got
> the following error:
> I also tried modifying the command to use the python compiler I got
> pre-installed in my Ubuntu 16.04, but I got an ImportError:
> Have I done something wrong? Please help me.
You can use --enable-python=fully-internal as a autogen flag (e.g. in autogen.input or autogen.lastrun) or set PYTHONPATH and URE_BOOTSTRAP in the execute.sh script.
We do not have a manual test system anymore and I believe all the test cases were converted. Closing.