Week 3 Report

Hello all,

The last week was the Third week of coding weeks in GSoC program. I continued adding support for the non supported items.

 Report in points:
  • Merging Writer Comments support .
  • Add demo to Writer Comment .
  • Add support for Dropdown items in grid window .
  • Add support for Calc comments .

1) The last week I left the Writer Comments item in this patch not merged. But now it's merged.

=====================================

2) I also created 2 test cases here in this patch. They test the Writer comment using the UITest framework. But the test cases appear to randomly fail. So the test cases was reverted here in this patch. The commit message has the details of the failure.

I worked in investigation of why this test cases fail randomly. By trying to run the old test case multiple times locally. The problem was when you execute Command to add new comment . Sometimes the comment doesn't have enough time to be created and added as a child in the MainWindow Object So test case fails.

I tried to add "time.sleep(1)" line to make sure that the comment created and added to the MainWindow as a child. But it wasn't a good solution.

So the fix in this patch was recommended by to use this function: 
"ui_test.wait_until_child_is_available(parent, childName)"
This will make sure that that the comment was created successfully and added as a child in the MainWindow to be selected in next lines. I also tried to run the test case again multiple times in my laptop and it never fails. The patch still under review.

=====================================

3) I also worked this week in Adding support for Dropdown items in grid window as we need to make test cases for issues similar to tdf#133855.

The support can be found in this patch add support for test cases that test Dropdown list of cells in Calc that can be created using:
Data -> Validity -> List
You can launch the list by this line for example:
gridwin.executeAction("LAUNCH", mkPropertyValues({"SELECTMENU": "", "COL": "2", "ROW": "9"})
Then you can select items from the list by it's id or it's text by these lines after launching the list:
xWin = self.xUITest.getTopFocusWindow()
xlist = xWin.getChild("list")
xListItem = xlist.getChild('0')
xListItem.executeAction("DOUBLECLICK" , mkPropertyValues({}) )
Also I added a test case that can be found here .

In this video I just want to show the results of this support:
=====================================

4) Finnaly, last week I worked on another item which was "Calc - comments" the work is here in this patch.

Now you can use these lines to use comments in calc test cases:
  1. Open Comment Window :  
    gridwin.executeAction("COMMENT",mkPropertyValues({"OPEN":""}))
  2. Then Type text as normal :
    gridwin.executeAction("TYPE",mkPropertyValues({"TEXT":"any"}))
  3. Close Comment Window : 
    gridwin.executeAction("COMMENT",mkPropertyValues({"CLOSE":""}))
  4. Write Comment without opening comment window: 
    gridwin.executeAction("COMMENT",mkPropertyValues({"SETTEXT":"any"}))

You can also check the comment text by this line: 
get_state_as_dict(gridwind)["CurrentCellCommentText"]

=====================================

Next week Tasks:
  • Finalize the demo of Writer comments and megre it .
  • Finalize the support Calc-comment patch and megre it .
  • Add test case for Calc-comments .
  • start working in Writer Format-Bullets and numbering dialog Selection.

Thanks for reading. And I am really interested to hear all your feedback and comments.

Comments

Post a Comment

Popular posts from this blog

GSoC'20 final report & Project Documentation

Image
  Overview      The idea was about The UI testing framework in LibreOffice. The UITesting  Framework is based on introspection code in c++ interacting with a testing framework in python through a simple UNO interface. To identify objects we use the ids that we introduced for loading dialogs from UI files. We were having unsupported items list in LibreOffice UITesting Framework. So The project mainly goals is to Extend the ability of the existing UI testing framework to support the unsupported items that exist now. So the work done on this list to decrease number of items in it.      As we also have a domain specific language that we used to log the events in its syntax and a Logger system that supports the UI elements of Visual Component Library and some application-specific events can also logged with the DSL syntax. Then to Increase the ability of the DSL that used for testing by Be able to log more complex events and the events of the new added items that were unsup
Read more

Week 11 Report

 Hello LO Community, The last week was the week 11 of coding weeks in GSoC program. I worked more on Adding support for new items in the uiLogger and the DSL.  Report in points:  Overall work.    FontWork Test case.  How to Add support for Item in the UILogger and the DSL.    ToolBar Support.  Calc LaunchMenu support.  Patch Status.   Next Week Tasks. =====================================   The last week I worked on this 3 things: 1) Make Sure that FontWork Features more well and add a test case for it. 2) Add Support for the ToolBar Actions. 3)Add Support for Launch Menu in Calc. =====================================   Also after investigation the Fontwork Gallery Dialog I found out that the selector of fontworks is also a ValueSet object. So the support is already added in this patch . I added here a demo has a test case to test the selector. You can find the test case in this patch . The Patch still under review. The Work was done to make sure that all Font Works items work.
Read more

Week 10 Report

Hello all, The last week was the 10th week of coding weeks in GSoC program. I worked more on adding support for new objects from the unsupported list.  Report in points: Overall work.  Select Presets and Shadow Styles in border tab ValueSet.  Fontwork Selector. "file properties- custom properties". ===================================== The last week I worked on this 3 entries from the unsupported items: 1) "Select Presets and Shadow Styles in border tab in format table or format cell". 2) "insert -> Fontwork". 3) "file properties- custom properties". The first 2 are done but the third needs more investigation and debugging. =====================================   After investigating format cell Dialog I found out that Presets and Shadow Styles used ValueSet for selection. So the work need to be done is to add support for the ValueSet. I added the support for the ValueSet here in this patch . This patch will add support for all the normal valu
Read more