-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
enhancementNew feature or requestNew feature or request
Description
as for now to run tests manually during release process we do:
0. provision cluster
- add Keycloak to cluster
- enable RBAC functionality
- enable history functionality
- enable audit logging
- enable multi-tenancy
enable opentelemetry tracing- set to all fixture-workers
STRICT_MODE: "false"
- set to
true
kodjin services: fhir-server-clickhouse-migrations, fhir-server-consumer-email-sender, fhir-server-converter, fhir-server-import-processor, fhir-server-job-consumer, fhir-server-job-producer, fhir-server-keycloak-config, fhir-server-metadata-builder, fhir-server-search-export, fhir-server-stream-subscription-processor, fhir-server-stream-summary-processor, fhir-server-subscription-sender, kodjin-data-mapper, kodjin-data-mapper-fixtures-worker, kodjin-data-mapper-mongodb-migrations, kodjin-fhirpath-helper, kodjin-minio-config, kodjin-terminology-console. - run test for your cluster. test repository - https://github.com/edenlabllc/kodjin.tests.
- After tests are finished i want to receive an allure report with results.
- tests should be started early in the morning, so that they are finished till 9am. After tests pass without any mistakes cluster should be destroyed. If there are troubles with cluster and we have all logs, cluster should be destroyed. if the percentage of tests less than 100% cluster should not be destroyed. (as for now we can't understand the % of passed tests, that will be done in future)
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request