Page Comparison

SIG Reports 2023-10-19

• SIG liaisons should check in with SIGs that seem to be not meeting or that have not provided a SIG report

Update on Quesnalia release timing

From Community Council: Please will you ask your councils to ratify the following change to our governance model concerning the CC size and quorum:

Current text:
    The council will have 15 members but can operate with a minimum of 9. The council will seek to have a diverse membership.
Proposed replacement:
    The community council will have 13 members but can operate with a minimum of 7. The council will seek to have a diverse membership.

This was approved by CC as noted in 2023-09-25 Meeting notes

Rationale is that initially a large CC was usefully representative but with 43 members that is no longer possible, it is better to have a smaller/tighter/more-engaged CC that handles necessary business effectively, works with PC and TC, and  works to support engagement from all members

Current state of FOLIO Quality Assurance testing

(link to ongoing discussion page)

Presentation by Yogesh of testing process with all its components

• testing happens during development - those are manual and automated tests
• there are manual test cases written by manual QA tster and POs
• POs review test cases and are stored in testrail repository
• In Sprint testing: unit tests, integration tests, daily e2e tests
• Release testing: Bugfest → repeat all tests for release ; consists of new features and regression testing
• timline: 2 week sprints
• manual test results: during sprints new features are tested and impacted test cases due to functional changes
• bugs are filed for failures; bugs go to triage process
• 904 automated test cases run daily
• ~ 9-10 bugs are found daily
• test cases in testrail are categorized: Smoke, Critical Path and Extended Path tests
• tests are repeated as part of the release cycle - by MQA and Community testers
• test cases are at least executed once until release
• number of automated test cases is growing (e.g. Critical Path tests currently 50% manual, 50% automated)
• more stats in Appendix slides
• Kristin: what are the definitions for the different test types
• Smoke = basic test, e.g. is the data correct
  • Defines most critical functions related to the feature availability or stability.  
• Critical Path = Test case covers critical data set that functionality should correctly process and returns an expected response. 
• Extended Path = Test case that covers other scenarios that make no impact on the feature's work or edge cases.
• definitions from: /wiki/spaces/DQA/pages/2661490
• Tod is there any plan of bringing community test to an earlier stage in the process? Maybe in the  iddle in the release cycle?
  • Khalilah: Yes, UATs should happen earlier, are organised by POs
  • but there are some challenges; will be topic at an upcoming PO meeting
• Jenn: it is more for the POs and more for the SMEs
  • looking at testrail runs: is there effort in decreasing the "noise" in bugfest? Would be good to get bugfest more focused as the automation increases
  • Yogesh: this might be an error, please ping Yogesh if you see something like this
• Jenn: SMEs could do more UATs;
• Khalilah in chat: Also sometimes we have trouble getting UAT participation.
• Jenn in chat:  As a sporadically participating SME, I know! This might be another conversation to have about why with the SMEs
• Kristin in chat: I think the Acq SIG has had a lot of success with UAT testing.
• Jenn in chat:  UAT becoming more prominent than bugfest seems like it would be great
• Yogesh: all test cases in testrail are manual tests, the aim is to bring the number down

Presentation by Oleksii on timeline

• Timeline includes: Development freeze, Module release, Bugfest, Bugfix, General announcement
• goal: up to dev freeze everything is finished
• module release is to test dependencies and whether modules are comaptible with next release; release notes should be updated
• bugfest: bugfest environment prep and test case execution; collecting feedback
• bugfix. fixing issues, final smoke test, final update of release notes
• general announcement of release via Slack