Week 11 Report

This week:

1) I have worked in solving the problem of un-named parent :
For example, if I open calc and select any cell you will find a field in the upper tab that has the name of the cell for example C10. If I tried to type another name in this I will get this log statement:

>>Type on 'pos_window' {"TEXT": "a"} from

This means that the 'pos_window' edit UI object has a parent with no name. So how to solve it and how to generate a UI test Case that corresponds to this action as I know I should convert it to something like this:

pos_window = [Parent_Name].getChild("pos_window")
pos_window.executeAction("TYPE", mkPropertyValues({"TEXT": "a"}))

This problem happens in many unexpected places and it makes the compiler stuck in running and not convert the logger to a UI test.

The easiest fix is to change the logger to recursively query the parent until you find an element with a name. Usually, that should work. IF you reach the top level and still have no parent, for the time being, we can assume that we can just use the top-level UI element.

I tried to make this but I found that the un-named parent has also a un-named parent and if I try to make a recursive loop it enters an infinite loop and the app crashed. Then I find that some of the un-named parent objects still have un-named parent after using this function:
https://opengrok.libreoffice.org/xref/core/vcl/source/uitest/uiobject.cxx?r=76806232#109

So try to find a solution that has a way to say that it is the current top-level parent. That does not mean the main window as there are quite a few dialogs that are not in the main window hierarchy. So I assume that only the parent can be a dialog so I modify the dsl_logger with these modifications:
  • Add recursively query for the parent until finding a parent with a name
    • This can be found in these functions
      vcl::Window* get_top_parent(vcl::Window* window)
      in the logger.cxx file
  • Remove the parent part "from xxxxxx" from the log statement if there is a un-named parent
  • Update the compiler to use the most top parent if there is command with no un-named parent:
    • This can be done in the dsl_core.py file with the file last_parent array that saves all the dialog in a hierarchy way to be able to get the top of them by access the array with the parent_hiraricy_count variable.


Then I test the new approach with many cases and it works efficiently the only problem if we have a dialog that has no name.

all this work can found here in this commit:
https://gerrit.libreoffice.org/#/c/77231/


2) Raal start to test the new logger with many test cases to be able to merge into the master in the future.

3) add missing footer line here: https://gerrit.libreoffice.org/#/c/77429/

Next week:
It will be the last week in the program so I will try to make good documentation for the project to be able to extend in the future and to describe all the used technologies in the project.

Comments

Post a Comment

Popular posts from this blog

GSoC final report

Image
  Overview The idea of this GSoC project was to implement new Domain-Specific language for LibreOffice to be used in UI testing by logging the user interactions with LO applications then generate the python code needed for the python UI framework which will make testing easier. Also, the project aims to improve the logger that logs all the user interaction to be logged in the new DSL syntax to be more readable. Then we can use this replaying all the user interactions as a UI test. Achievements Grammar of new DSL done for starter_commands uno_commands dialog_commands  General_commands   Grammar that are general for all application. UI_Object_commands This support: ButtonUIObject EditUIObject CheckBoxUIObject RadioButtonUIObject  ListBoxUIObject  ComboBoxUIObject SpinUIObject  TabControlUIObject Special_commands This is for the logging of different applications actions: Writer Type Select GOTO page Calc Type Select cell or range laun
Read more

UI Logger

This post is just documentation for GSoC Project of UI logger here: https://summerofcode.withgoogle.com/projects/#5252265672179712 This project is to generate a new easier Domain-Specific_language for logging the user interactions to be able to convert it to a python script that used by python UI framework for testing. This project made with Textx which is a meta-language for building Domain-Specific Languages (DSLs) in Python. it helps you build your textual language in an easy way. You can invent your own language or build support for already existing textual language or file format. If you need to understand how the project is written and mainly the part in this folder: https://opengrok.libreoffice.org/xref/core/uitest/ui_logger_dsl/ I think you can easily see the tutorials here of TextX. The basics of this tutorial that you can understand with 30 mins can let you understand a lot of the project. WHY DSL? DSL is a very useful thing because it lets us understand the code
Read more

Week 8 Report

Image
This week: (The report may look very long but this is because of images only) I start testing the performance of the new UI logger. I tried this by opening the LO and start to make some actions and log the actions and convert it to a UI test. I will add here these examples of the generating logs that include most of the logger features and the corresponding generated python UI test. writer   these logs==>>  Generates this UI test ==>> Calc  these logs==>>  Generates this UI test ==>>  And by similarity, we can try math and impress... ============================================================== ============================================================== Also, I was having a problem 1) while trying to move between the UI Objects with the keyboard I got these old logs :  I worked on this and convert it to be: 2) Also solve some problems in UNO Commands that appears when you have 2 parameters. ========
Read more