Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

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.

  • Kafka issues resulting in issues that looked like code issues but where instead failures in messages being delivered.

TestRails issues

  • Users have to asked to be assigned accounts, this is a hurdle that they must get over before they can even see the test cases.

  • There are a lot of projects in TestRails, which makes it more difficult to navigate to the correct project used for BugFest.

Issues with BugFest Data

Inventory

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) 

image-20240405-132906.pngImage Removedimage-20240405-132917.pngImage Removed

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:

Agreements

Orders

MARC Authority

General concerns:

Suggestions:

  • Sigs work with POs to provide base testing data which is populated to the hosted reference environments. [1]

  • Based data is updated and merged with the base image data as needed. [1]

Bugfest

  • Refresh inventory data

  • Create a more realistic setup

TestRails

Footnotes:

Anchor
[1]
[1]
- Conclusions derived from Slack Comments 4/3/2024