SoK/2023/StatusReport/Rishi Kumar: Difference between revisions
| Line 34: | Line 34: | ||
=== Week 5 and Week 6 === | === Week 5 and Week 6 === | ||
The CI pipelines of tokodon were failing due to the tests performing settings read/write operations which were not required while testing, the maintainers of Tokodon helped me identify this issue and made a commit to fix the issue [https://invent.kde.org/network/tokodon/-/commit/78504f9784398b0815571024dfacc81ca25eaac0 here]. | |||
I also wrote a mid-journey [https://k3yss.github.io/posts/sok_blog1/ blog post] about my Season of KDE experience in these weeks | |||
=== Week 7 and Week 8 === | === Week 7 and Week 8 === | ||
Revision as of 18:25, 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
- Merge Request for testing Status.
- Merge Request for testing Search
- Merge Request for fixing the broken search UI in tokodon-offline
- Merge Request for making tokodon-offline executable.
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
The CI pipelines of tokodon were failing due to the tests performing settings read/write operations which were not required while testing, the maintainers of Tokodon helped me identify this issue and made a commit to fix the issue here.
I also wrote a mid-journey blog post about my Season of KDE experience in these weeks