Skip to end of metadata
Go to start of metadata
 

Goal:

  1. Assess effectiveness of automated tests
  2. Suggest additional quality improvements

Agenda:

  1. Review defects for Juniper release:  https://issues.folio.org/secure/Dashboard.jspa?selectPageId=11833
    1. How many BE defects had missing unit test
    2. How many BE defects has missing Karate test
    3. How many FE defects had missing unit test
    4. How many FE defects had missing E2E test
    5. How many defects related to missing requirements
    6. Any architecture related bugs: check-in/check-out, loans, anonymization, reporting
    7. Additional recommendations to prevent existing defects
  2. Separately, review Regression defects and identify common root causes
  3. Propose process changes that can improve quality
  4. Any other groups of tests are missing or needed
  5. Suggestions for test environment improvements
  6. Propose desired team composition: 
    1. Number of FT manual testers
    2. Number of FT automated testers (BE and/or FE)

Retrospective





https://issues.folio.org/browse/UICIRC-667Is regressionNo extra test coverage was introducedN/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 addedUnit 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-1178Architecture 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-1187Requirement bugFix the behaviour and create test coverageNo type of tests would have prevented it
https://issues.folio.org/browse/UIU-2229Requirement bugFix the behaviour and create test coverageNo type of tests would have prevented it
https://issues.folio.org/browse/UIREQ-629Architecture issueRevise the approach for reports generationNo type of tests would have prevented it
https://issues.folio.org/browse/UIREQ-627
Edge caseUnit test would have prevented it
https://issues.folio.org/browse/UIU-2224

Unit test would have prevented it
https://issues.folio.org/browse/UIIN-1556Is 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 standardsNo 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-24Requirement bugFix the behaviour and create test coverageNo type of tests would have prevented it
https://issues.folio.org/browse/UICHKOUT-720
Edge caseNo 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 introductionN/A