Showing posts from August, 2019

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…

Week 10 Report

This week:

1) I tried to work on the Some draw and Impress to log more events on them but the problem was that they were having the same function that they call to perform similar operations.

To Solve This for example for the:
Add_Slide    ====> in impressAdd_page    ====> in draw I add these events to the logger in this Commit: So now we have these log Statements for examples:
Insert new Slide at position 3   ====> in impressInsert new Page at position 3   ====> in draw2) In the Same Commit (this one) I make a modification in the UITestLogger class to be able to know the difference between the draw and the Impress log statements and be able to store the current working app information.

3) Also add some new events to be supported with our UI logger like:
 ImpressInsert SlideDelete SideDuplicate Slide Rename SlideDrawInsert PageDelete PageRename PageThis Work Can be found here:
4) Log More Events: