Issues with the testing environment
Several login issues appeared during testings, usually users where locked out the main FOLIO account as well as accounts they created.
TestRails issues
Issues with BugFest Data
Inventory
Multiple duplicate records: Example https://bugfest-quesnelia.int.aws.folio.org/inventory/view?filters=holdingsType.1d353b7b-24d8-469d-b9ab-944eaea8645d%2CstaffSuppress.false&segment=holdings&sort=title
Resource access
Settings are specific to test cases. It makes it very difficult to double check if there is an issue or test fringe cases. Doing so requires building all aspects of the circ polices from scratch, including adding calendars to service points.
General concerns
https://folio-project.slack.com/archives/G9FUXCJDD/p1712123744899809
Thomas Trutt, kg - along the same lines as Thomas raise for Bugfest environments, then the Product Council also has talked about, that a way to do better early test of new work, would be if we in general could get in real data in FOLIO Snapshot environments, e.g. the 36 bibliographic records (source = folio) in Inventory are records added more than 5 years ago, and today in a state of very incomplete descriptive catalogued records. And on top of this with all the automatic tests happening then this makes FOLIO Snapshot data to be in a state with weird looking data. Similar for other apps like Agreements, Orders, MARC Authority, etc. (edited)
One suggestion could be that the respective SIGs for each app (domain) work with the POs and provide updated data, which the DevOps building the hosted reference enviroments, then capture, and save as new sample data. Maybe we can even add more data than what we currently have; but still a small data set, so it does not slow down the daily build of these reference environments
Suggestions:
Bugfest
Refresh inventory data
Create a more realistic setup