Date 03 Apr 2025

Agenda

• Discuss issues raised in the UI and test management

• Address CI QA test failure concerns

• Team member progress updates

• Guidance on writing integration and unit tests

• Debugging support for team members

• Dependency and configuration issues in test setup

• GSoC mentorship and contribution tips

 Participants

Agaba Derrick
Rahul kundu
Aditya Aditya
Lemeri
Nathan Silver
Herbert
Soham
Segujja Joseph
Brian Bahati
Vaishnavi
Debz
Atul Yadav
Govind
Dev
Govind

Notes

• UI Breadcrumb Issues:
  Lemeri raised concerns about breadcrumb behavior in the test management UI. Aditya advised against making changes, noting that it aligns with the behavior of the legacy UI.

• CI QA Test Failures:
  Derrick inquired about recurring continuous integration (CI) QA test failures.
  Aditya explained that failures may occur during peak usage hours and encouraged everyone to continue pushing code regardless, keeping this in mind.

• Derrick’s Updates:
  Derrick presented two works from the week:

  • PR #1817

  • PR #1740 (previously failing last week)

• Aditya’s Updates:
  Aditya shared minor fixes, including some that were non-code-related.

• Integration Testing Guidance (Segujja):

  • Emphasized the importance of following class testing order and adhering to DBUnit conventions when writing integration tests.

• Rahul’s Inquiry on Writing Tests:

  • Rahul Kundu asked for help with writing unit and integration tests.

  • Joseph assisted by walking him through tested service classes (e.g., GenderServiceTest).

  • Advised tracing method behavior to the DAO level for clarity on how data is persisted, enabling better test writing.

• Framework & Test Config Insights (Joseph):

  • Explained the role of BaseWebContextSensitiveTest in configuring DB connections and dataset management.

  • Highlighted that it handles automatic cleanup of data post-test.

  • Guided Rahul through AppConfig, focusing on the component scan used test setup.

  • Shared an additional example of a written test via a sample integration test.

• Debugging Assistance:

  • Deby requested Joseph’s help with debugging her test work.

• Test Updates Inquiry (Herbert):

  • Herbert asked if anyone had further updates on integration test work.

• Component Scan Dependency Issue (Adarsh Samani):

  • Reported a dependency issue in the component scan.

  • Was advised to post the error in Slack for further assistance.

• GSoC Tips:

  • Adash asked Herbert for Google Summer of Code (GSoC) tips regarding Integration Test project.

  • Herbert advised contributing to any testable part of the codebase that has not been tested yet.

Govind’s Issue:

• Encountered an error while running the container after adding a new package to /frontend/package.json.

• Herbert advised rebuilding the Docker images a fresh to resolve the issue.

 Action items

• Team members should continue pushing code despite intermittent CI failures.
• Follow DBUnit testing conventions and test class structure.
• Rahul to explore DAO layers for better test understanding.
• Adashsamani to post his component scan error in Slack.
• Govind to rebuild Docker images after updating /frontend/package.json.
• Joseph to assist Deby with debugging.