Goal:
- Assess effectiveness of automated tests
- Suggest additional quality improvements
Agenda:
- Review defects for Juniper release: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=11833
- How many BE defects had missing unit test
- How many BE defects has missing Karate test
- How many FE defects had missing unit test
- How many FE defects had missing E2E test
- How many defects related to missing requirements
- Any architecture related bugs: check-in/check-out, loans, anonymization, reporting
- Additional recommendations to prevent existing defects
- Separately, review Regression defects and identify common root causes
- Propose process changes that can improve quality
- Any other groups of tests are missing or needed
- Suggestions for test environment improvements
- Propose desired team composition:
- Number of FT manual testers
- Number of FT automated testers (BE and/or FE)
Retrospective
https://issues.folio.org/browse/UICIRC-667 | Is regression | No extra test coverage was introduced | N/A |
https://issues.folio.org/browse/UIREQ-628 | E-2-E would have prevented it | ||
https://issues.folio.org/browse/UIU-2214 | Edge case. FE unit test for empty string and missing value should be added | Unit test would have prevented it | |
https://issues.folio.org/browse/UIREQ-626 | E-2-E would have prevented it | ||
https://issues.folio.org/browse/CIRC-1178 | Architecture issue | No type of tests would have prevented it | |
https://issues.folio.org/browse/UIIN-1546 | E-2-E would have prevented it | ||
https://issues.folio.org/browse/MODINVSTOR-759 | No type of tests would have prevented it | ||
https://issues.folio.org/browse/MODRTAC-64 | Unit test would have prevented it | ||
https://issues.folio.org/browse/CIRC-1187 | Requirement bug | Fix the behaviour and create test coverage | No type of tests would have prevented it |
https://issues.folio.org/browse/UIU-2229 | Requirement bug | Fix the behaviour and create test coverage | No type of tests would have prevented it |
https://issues.folio.org/browse/UIREQ-629 | Architecture issue | Revise the approach for reports generation | No type of tests would have prevented it |
https://issues.folio.org/browse/UIREQ-627 | Edge case | Unit test would have prevented it | |
https://issues.folio.org/browse/UIU-2224 | Unit test would have prevented it | ||
https://issues.folio.org/browse/UIIN-1556 | Is regression | Unit test would not have prevented it | |
https://issues.folio.org/browse/UIPFI-36 | E-2-E would have prevented it | ||
https://issues.folio.org/browse/UICAL-148 | This code was mess. Does not correspond to project standards | No type of tests would have prevented it | |
https://issues.folio.org/browse/UIIN-1534 | Unit test would not have prevented it | ||
https://issues.folio.org/browse/UIPCIR-24 | Requirement bug | Fix the behaviour and create test coverage | No type of tests would have prevented it |
https://issues.folio.org/browse/UICHKOUT-720 | Edge case | No type of tests would have prevented it | |
https://issues.folio.org/browse/MODRTAC-56 | Unit test would have prevented it | ||
https://issues.folio.org/browse/MODINVSTOR-719 | Not an issue. New requirement introduction | N/A |