Week 4 Report

This week:

As this week was my last week in my exams I worked in many minor points to finish it and finish all missing parts for phase1.

I migrate all the work in this branch :
                                 >  private/EL-SHREIF/ui_logger
This will make it easy to work on the old commits then we can merge at the end of the project.

as I found we have many lines that we will not use in the compiler in the future for example these lines:
        Action on element: urled with action : TYPE
        Action on element: urled with action : 16

So I solve this by make this function :
        OUString WindowUIObject::get_action(VclEventId nEvent) const
return empty string when we don't need to log this statement I think this won't be the best approach in the future.

this is example of what we can get now from the new logger:



Also for adding Jinja2 to use it in generation. I tried this week to create simple data structure that we can use to make same thing without any need to add external resources.

Also this week the SideBar actions wasn't implemented so I add it to the grammar as a general commands as it will be the same for all the applications.

Also this week the Select actions wasn't logged with the new grammar. I add it to the grammar as a general commands also. it will be like this:
                              >>Select  {"OBJECT": "Unnamed_Obj_0"}

Also This week I worked on adding the special command for math and impress in the grammar and write the log statements with the new grammar.

all this can be found in this patch: https://gerrit.libreoffice.org/#/c/74629/

So for phase 1 we have:
1) grammar for the new ui_logger
2) all the log statements now worked with the new grammar

to finish the project the next stage will be:
1) working on the compiler that will generate the test cases from this grammar
2) start adding new events to be logged

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