SoK/2023/StatusReport/Rishi Kumar: Difference between revisions

Revision as of 17:46, 11 April 2023

Accessibility: Work on improving the accessibility of Tokodon

This project aims to improve the accessibility of tokodon by writing appium tests.

Writing these tests would ensure a set standard of code quality is maintained in tokodon and with improved accessibility leading to a more efficient and convenient experience for the end users.

Mentor

Carl Schwan

Merge Request

Blog Posts

Timeline

Week 1 and Week 2

The first couple of weeks went on in researching how I would start tokodon without network connectivity, it was achieved by creating a new entry point named main-offline.cpp with the account initialised as the object of MockAccount class following which I created an executable named tokodon-offline by making relevant changes in src/CMakeLists.txt. The merge request for the implementation can be found here.

Week 3 and Week 4

The following two weeks were spent on writing appium test for search functionality. For this, I first had to make the search function in tokodon-offline, for achieving this I studied the already unit-tests for search and found out the code made mock API calls and received the search results through a search-result.json file so I followed the same approach and made the same mock API calls to receive search responses after which I was successful in making the search function. The merge request for this implementation can be found here

Once the search functionality was implemented, my next task was to write appium test for it, for which I referred to Harald's blog for the implementation, the merge request for search appium test can be found here

Week 5 and Week 6

In these weeks I, with the help of the maintainers of Tokodon, fixed the breaking pipelines of tokodon-offline and wrote another appium test for testing different types of timeline statuses and also published my 1st blog post.

@@ Line 28: / Line 28: @@
 === Week 3 and Week 4 ===
-The following two weeks were spent on writing appium test for search functionality. For this, I first had to make the search functional in tokodon-offline, for achieving this I studied the already unit-tests for search and found out the code made mock API calls and received the search results through a search-result.json file so I followed the same approach and made the same mock API calls after which I was successful in making the search functional. The merge request for this can be found [https://invent.kde.org/network/tokodon/-/merge_requests/155 here]
+The following two weeks were spent on writing appium test for search functionality. For this, I first had to make the search function in tokodon-offline, for achieving this I studied the already unit-tests for search and found out the code made mock API calls and received the search results through a search-result.json file so I followed the same approach and made the same mock API calls to receive search responses after which I was successful in making the search function. The merge request for this implementation can be found [https://invent.kde.org/network/tokodon/-/merge_requests/155 here]
+Once the search functionality was implemented, my next task was to write appium test for it, for which I referred to [https://planet.kde.org/harald-sitter-2022-12-14-selenium-at-spi-gui-testing/ Harald's blog] for the implementation, the merge request for search appium test can be found [https://invent.kde.org/network/tokodon/-/merge_requests/168 here]
 === Week 5 and Week 6 ===