GSoC 2025: Improving E2E QA tests Project thread

I’m excited to share that I’ve been selected as a GSoC 2025 contributor. It’s a great opportunity to make a meaningful impact.

I’m Brian Patrick Bahati, also known as @tasksolver, and this thread will serve as the space for updates related to the project “Improving E2E QA Tests.” I’m looking forward to collaborating with the entire community, and I’m especially grateful to be working under the mentorship of @Gita_cliff.

If you have any questions or suggestions, feel free to tag me — I’ll do my best to respond promptly.

For more details about the project, you can check it out here

Project Approach
Phase 1: Assessment and Planning
● Conduct a comprehensive audit of the current E2E test coverage.
● Identify untested critical functionalities.
● Define key testing scenarios and user workflows to be covered.
● Establish a roadmap and timeline for test implementation.

Phase 2: Test Development
● Write new E2E test cases focusing on uncovered functionalities.
● Ensure tests cover user authentication, data management, and critical UI interactions.
● Implement best practices to maintain test stability and reliability.

Phase 3: Test Optimization
● Refactor existing test cases to improve efficiency.
● Optimize test execution time to prevent slowdowns in development workflows.
● Ensure tests are resilient against minor UI changes.

Phase 4: Integration into CI/CD
● Configure automated test execution in the CI/CD pipeline.
● Set up reporting mechanisms to track test results and failures
● Implement alerts for failed tests to ensure quick resolution.

Phase 5: Documentation and Knowledge Sharing
● Develop comprehensive documentation on test implementation and maintenance.
● Conduct training sessions for developers and QA engineers.
● Establish guidelines for maintaining high test coverage moving forward.

Expected Outcomes
● Increased E2E test coverage from 30% to at least 99%.
● Reduced risk of undetected critical bugs.
● Faster detection and resolution of issues before deployment.
● Improved confidence in system reliability and stability.
● Sustainable testing strategy integrated into the development lifecycle

cc: @Gita_cliff @Moses_Mutesasira
#OpenELIS #GSoC25 #E2E #QATests #Cypress #React #TypeScript #JavaScript

3 Likes

welcome @tasksolver , congratulations and happy to work with you :100:

2 Likes

Hello @Community: Great News To Announce;

●Audit of the current E2E test coverage Report and untested critical functionalities/components[WIP].

It is part of Phase 1: Assessment and Planning.

The report can be found right here . Feel free to advise, comment and guide.

Related issue: Yeah, I am the issue
On jira: I am the jira ticket
Related PR: Hey, I am the PR he said

Regards: Brian, @tasksolver .

cc: @Gita_cliff , @Moses_Mutesasira

Community > GSOC gsoc2025 #E2E

2 Likes

Hello Community, here is the summary of how my Community Bonding Period ( May 8 - 1 June ) was spent.

  1. Got a wonderful welcome from my mentor @Gita_cliff , and we discussed some ideas related to the community and the project at large.
  2. Opened threads for progressive reporting to the community for advice and guidance.
  3. Made review (audit) of the current tests and came up with a report.
  4. Opened an issue basing on the blocker I got from the PR I raised.
  5. Summed up the period with new challenges that I am beginning with in this coding period.

In case of any inquiries, feel free to tag me at @tasksolver .
Big-up to @Gita_cliff , @Moses_Mutesasira and the whole community.

Regards;
Brian @tasksolver

Community > GSOC gsoc2025 Community > Development #E2ETests #OpenELIS

2 Likes

GSoC 2025: CODING SESSION UPDATES JUNE 2-9, 2025

Hello OpenELIS Community:
The first week in the coding phase has been marked by ups and downs, but above all full of challenges to tackle – and challenges make us grow.

During this past week, the Phase 2: Test Development was opened which is marked by;
● Write new E2E test cases focusing on uncovered functionalities.
● Ensure tests cover user authentication, data management, and critical UI interactions.
● Implement best practices to maintain test stability and reliability.

Particularly: Write new E2E test cases focusing on uncovered functionalities.
PR opened: Dictionary Menu E2E.

Blocker: All tests were initially failing due to importing a wrong file.
Fix: Imported the correct file after a long hustle and bustle.

Flashback: After opening this PR, it led to opening these issues 1, 2, 3, 4, 5. By @Moses_Mutesasira and I which were worked upon by @Lemeri123 with these PRs 1, 2, 3 which are under review.

Way forward: After reviewing the PRs, and get merged, the user management E2E will be completed and ready for merging.

Vote of thanks to @Gita_cliff , @Moses_Mutesasira and @Lemeri123 for the advice, contribution and guidance.

Regards
Brian, @tasksolver .
#OpenELIS #GSoC25 #E2E #QATests #Cypress #React #TypeScript #JavaScript

3 Likes

GSoC 2025: CODING SESSION UPDATES JUNE 9-16, 2025

Hello OpenELIS Community:
The second week in coding session went on as follows;

During this past week, the Phase 2: Test Development was opened which is marked by;
● Write new E2E test cases focusing on uncovered functionalities.

Particularly: Write new E2E test cases focusing on uncovered functionalities.
PRs opened: Barcode-E2E
Fix : Dictionary Menu Fix

Feature: Reflex Tests Configuration

Big-up to @Gita_cliff , @Moses_Mutesasira and @sharif for the advice and guidance.

Always Coding:
Brian, @tasksolver .

#OpenELIS #GSoC25 #E2E #QATests #Cypress #React #TypeScript #JavaScript