https://github.com/liquibase/liquibase-test-harness

This is a Harness of Integration Tests designed to validate Liquibase behavior
https://github.com/liquibase/liquibase-test-harness

Last synced: about 1 month ago
JSON representation

This is a Harness of Integration Tests designed to validate Liquibase behavior

• Host: GitHub
• URL: https://github.com/liquibase/liquibase-test-harness
• Owner: liquibase
• License: apache-2.0
• Created: 2020-08-13T16:23:15.000Z (about 5 years ago)
• Default Branch: main
• Last Pushed: 2024-11-19T16:43:01.000Z (11 months ago)
• Last Synced: 2024-11-19T17:12:08.359Z (11 months ago)
• Language: Groovy
• Homepage:
• Size: 8.32 MB
• Stars: 13
• Watchers: 14
• Forks: 16
• Open Issues: 14
• Metadata Files:
  • Readme: README.advanced-test.md
  • License: LICENSE

Awesome Lists containing this project

README

          
## Advanced test

* The test behavior is as follows:

    * The test reads sql script provided in `src/main/resources/liquibase/harness/compatibility/advanced/initSql/primary` folder

    * `liquibase executeSql` is then executed to deploy script to the primary DB instance

    * The test takes a snapshot of the database after deployment by running Liquibase 'snapshot' command

    * Actual DB snapshot is compared to expected DB snapshot (provided in `src/main/resources/liquibase/harness/compatibility/advanced//expectedSnapshot`)

    * If snapshot is correct, the test then runs `liquibase generateChangelog` for all supported changeset formats (xml, sql, yml, json)

    * For all modeled changelog formats the test verifies generated changelog contains required changeset, that should be the same as initSql file name (if initSql was `createTable.sql`, the test will search for createTable changeset)

    * For sql format the test compares query from generated changelog with expected query (provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedSql/generateChangelog`)

    * If validation was successful, the test then runs `liquibase updateSql` on generated changelog to generate query

    * Compares generated query with expected query (provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedSql/generateChangelog`)

    * If expectedSql is not provided, validation is skipped and auto-generated sql script is saved to `src/test/resources/liquibase/harness/compatibility/advanced/expectedSql/generateChangelog`

    * The test runs `liquibase diff` command referencing secondary DB instance

    * Compares generated diff with expected diff, provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedDiff`

    * If generated diff is correct, the test then runs `liquibase update` to deploy generated changelog to secondary DB instance

    * The test runs `liquibase diff` command again

    * Compares generated diff with expected diff, provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedDiff/empty.txt` to verify no differences between two instances

    * Secondary instance is then cleared by running `liquibase dropAll` command

    * The test then runs `liquibase executeSql` with sql script, provided in `src/main/resources/liquibase/harness/compatibility/advanced/initSql/secondary` folder

    * The test then runs `liquibase diffChangelog` for all supported changeset formats (xml, sql, yml, json) referencing secondary instance

    * For all modeled changelog formats the test verifies generated changelog contains required changeset, that should be the same as initial changelog name, as well as reversed changeset (if initial changelog was `createTable.xml`, the test will search for createTable and dropTable changesets)

    * For sql format the test compares query from generated changelog with expected query (provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedSql/diffChangelog`)

    * If validation was successful, the test then runs `liquibase updateSql` on generated changelog to generate query

    * Compares generated query with expected query (provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedSql/diffChangelog`)

    * If expectedSql is not provided, validation is skipped and auto-generated sql script is saved to `src/test/resources/liquibase/harness/compatibility/advanced/expectedSql/diffChangelog`

    * If query is correct, the test then runs `liquibase update` to deploy diff changelog to secondary DB instance

    * The test runs `liquibase diff` command referencing secondary DB instance

    * Compares generated diff with expected diff, provided in `src/main/resources/liquibase/harness/compatibility/advanced/expectedDiff/empty.txt` to verify no differences between two instances

    * Both DB instances are then cleared by running `liquibase dropAll`

    * Finally, the test deletes all generated changelogs from `src/test/resources/liquibase/harness/compatibility/advanced/` folder