-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
- Loading branch information
Showing
8 changed files
with
24,942 additions
and
49,327 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# Integration tests | ||
|
||
Steps to update the integration tests for the latest supported version: | ||
|
||
1. Update the postgres image in the `postgres-latest-supported` of the [docker-compose](./docker-compose.yml). | ||
2. Execute the integration tests | ||
* If the JSON-schema validation fails: | ||
- Check the inventory, some server settings might have been removed. | ||
- Check the number of entities: the number of internal tables and or indexes may vary (metrics failures). | ||
- Check the release notes ([Postgres 16 example](https://www.postgresql.org/docs/release/16.0/)) | ||
3. Once the failures are understood (if any), update the corresponding JSON-schema files, you may need to generate it | ||
using the integration output, specially if there is any metric failure. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.