Review state control of modules
Description
Environment
None
Potential Workaround
None
is cloned by
is defined by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Oleksii Popov October 12, 2020 at 3:20 PMEdited
We expect to understand where changes are needed.
All information is tracking on this ticket.
More information about scaling is listed here: https://docs.google.com/document/d/1kmafhus497R5UF1D3GxJb3QoJMRPvBdadfolGVkq6G0/edit
Marc Johnson October 12, 2020 at 2:28 PM
What is the expected output of each of these tasks? Is this information being collected somewhere? How is it going to be used?
Marc Johnson October 12, 2020 at 2:27 PM
Has the definition for state control been agreed upon, allowing teams to perform this evaluation?
Details
Details
Assignee
Unassigned
UnassignedReporter
Oleksii PopovPriority
TBDDevelopment Team
None
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created August 17, 2020 at 12:21 PM
Updated July 11, 2022 at 9:08 PM
TestRail: Cases
TestRail: Runs
In order to achieve a possibility to run multiple instances of the same module state control verification should be done.
Each team should verify their back-end modules code in order to ensure that the module is stateless.
In another case - raise it and each module technical design should be reviewed separately.
Teams responsibility for modules: https://folio-org.atlassian.net/wiki/display/REL/Team+vs+module+responsibility+matrix