Skip to:

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

Schema Upgrade Testing

Description

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

wrote some documentation for doing this locally.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Viacheslav Kolesnyk February 17, 2022 at 11:21 AM

Testing was performed in the following way:

  1. Started local vagrant box 'folio/release' version '1.0.0-20220210.7508'.

  2. Filled database with data using UI - added different notes for users, titles, packages.

  3. Posted new tenant and enabled module for it.

  4. Upgraded module to the latest version '3.0.0' and enable it for both tenants.

  5. Verified all liquibase updates completed successfully in module logs- for both tenants (filled with data and empty one).

  6. Verified all liquibase updates completed successfully according to database's 'databasechangelog' table.

  7. Verified that all schema updates applied for both tenants through directly inspecting schema via pgAdmin.

  8. Verified that all data present and functionality working through UI.

  9. Posted additional tenant to new version of module.

  10. Verified schema successfully created for new tenant.

A bug was found and fixed during schema upgrade testing.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Parent

Fix versions

Release

Lotus R1 2022

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 18, 2022 at 1:24 PM
Updated February 17, 2022 at 3:15 PM
Resolved February 17, 2022 at 3:15 PM
TestRail: Cases
TestRail: Runs