Skip to content

Run functional test every night #70

@anovikov-el

Description

@anovikov-el

as for now to run tests manually during release process we do:
0. provision cluster

  1. add Keycloak to cluster
  2. enable RBAC functionality
  3. enable history functionality
  4. enable audit logging
  5. enable multi-tenancy
  6. enable opentelemetry tracing
  7. set to all fixture-workers STRICT_MODE: "false"
  8. 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.
  9. run test for your cluster. test repository - https://github.com/edenlabllc/kodjin.tests.
  10. After tests are finished i want to receive an allure report with results.
  11. 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 request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions