Charts[Test]: Implement smoke tests and integrate with CI/CD

leninmehedy commented 1 year ago

Requested Feature

We need a set of smoke tests to be run after the infrastructure is deployed to ensure port mappings are correct.

There are few manual smoke test scripts available that we run manually to ensure the infrastructure is operational. So it would be useful to have those automated as a separate Makefile target.

Some of the existing "manual smoke tests" are in the following directories:

/dev/gateway-api
/dev/telemetry

We could have a makefile target such as "make run-smoke-tests" that runs those smoke tests. This should also be run in the CI pipeline.

Business Need

Currently helm-chart tests only verifies if infrastructure components have been deployed or not. Smoke tests for port mapping can add extra confidence that the infrastructure is operational by running some basic e2e that tests for telemetry and gateway-api.

In addition, these sets of basic smoke tests should be run in CI-pipeline.

Additional Context

We could have these tests as part of the fsnetman CLI

### Tasks
- [ ] #316
- [ ] https://github.com/hashgraph/full-stack-testing/issues/426
- [ ] https://github.com/hashgraph/full-stack-testing/issues/427
- [ ] https://github.com/hashgraph/full-stack-testing/issues/428
- [ ] https://github.com/hashgraph/full-stack-testing/issues/429
- [ ] https://github.com/hashgraph/full-stack-testing/issues/430
- [ ] Charts[Test] Implement smoke test for platform node

leninmehedy commented 12 months ago

We shall implement this as part of the CLI

jeromy-cannon commented 5 months ago

would be good to use this feature to create unit, integration, and e2e tests for the helm charts. Some useful links to explore further:

Currently, we are still using the make files, and even the helm test <chart name> is not being used in the build process and has minimum functionality. Currently the build process is still using the makefile scripts.

hashgraph / full-stack-testing