Since i have seen that ibus-unikey currently is testing manually, travis-ci only uses for build and verify that the code can't build with latest libraries. We should find a simple way to test as the way the enduser usually does and we can build a better way to develop this project.
What has been done?
Build a generic pipeline to test directly with latest Ubuntu using virtual machine (VM).
Allow using VNC to connect directly to the VM to help to troubleshoot better.
Try to test with the simple test case, using dogtail to automate typing text to gedit, save it to file, open this file again and verify that what we typing are same with the text we instruct dogtail doing.
Description:
Since i have seen that ibus-unikey currently is testing manually, travis-ci only uses for build and verify that the code can't build with latest libraries. We should find a simple way to test as the way the enduser usually does and we can build a better way to develop this project.
What has been done?