Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Schema Upgrade Testing

Priority

Labels

Environment

None

Template

None

Description

Process described on #releases channel here https://folio-project.slack.com/archives/CGPMHLX9B/p1590164280223800

wrote some documentation for doing this locally.

Note: fill database with test data before testing schema upgrade.

Please test these scenarios when upgrading schema

  • Upgrading a library with multiple kbs setup

    • Any impact to user already assigned to KB credentials?

    • Any impact to use of eholdings app

      • Any impact to tags assignment/removal

      • Any impact to access status type assignment or removal

      • Any impact to usage consolidation

    • Any impact to exporting eholdings - does it only export holdings for the assigned set of EBSCO KB credentials

Development Team

Spitfire

Release

Morning Glory (R2 2022)

Story Points

Sprint

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Viacheslav Kolesnyk June 22, 2022 at 12:37 PM

Before migration:

  • set up 2 different valid kb credentials

  • assign 1 user to each of credentials

  • create some packages for each of credentials

  • add some tags for packages

  • create access types and assign to packages

  • set usage consolidation for one of kb credentials

  • create additional empty tenant

folio/release v1.0.0-20220509.7647 vagrant box doesn't seem to be appropriate for migration testing. Module replacement fails because of multiple versions registered and not the latest is installed.

So migration was tested by bringing up mod-kb-ebsco-java in docker along with postgres and wiremock(for users/groups api calls mock) and calling mod-kb-ebsco-java apis from postman.

Migration executed successfully according to logs:

After migration:

  • retrieve credentials

  • retrieve users assigned to credentials

  • unassign user

  • assign user

  • retrieve access types

  • create access type

  • delete access type

  • retrieve packages for different kb credentials and different filters

  • retrieve tags

  • assign/unassign tags

  • retrieve usage consolidation settings

Migration for empty tenant was executed successfully as well.

Tenant creation on new version performs correctly.

Export is done using regular mod-kb-ebsco-java apis thus no additional check is needed.

Done

Details

RCA Group

TBD

Assignee

Reporter

Fix versions

Parent

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created May 30, 2022 at 2:54 PM
Updated June 22, 2022 at 12:37 PM
Resolved June 22, 2022 at 12:37 PM
Configure
TestRail: Cases
TestRail: Runs