Skip to content

TESTING.md

Latest commit

 

History

History
99 lines (69 loc) · 1.96 KB

TESTING.md

File metadata and controls

99 lines (69 loc) · 1.96 KB

Testing OpenCTI Helm Chart

This document provides guidelines for testing the OpenCTI Helm chart. Follow these instructions to ensure the chart works as expected before deployment to production.

Steps

1. Lint Testing

# Run helm lint to check for any syntax issues
helm lint charts/openaev

2. Template Testing

# Generate and verify the template output
helm template openaev charts/openaev --debug

3. Local installation testing

# Install the chart in a test namespace
kubectl create namespace openaev-test
helm install openaev-test charts/openaev --namespace openaev-test

4. Verification steps

  1. Check all pods are running:
kubectl get pods -n openaev-test
  1. Verify services are exposed:
kubectl get svc -n openaev-test
  1. Check platform accessibility:
kubectl port-forward svc/openaev-test 8080:8080 -n openaev-test
  1. Validate component health:
  • OpenCTI platform UI accessibility
  • ElasticSearch connection
  • RabbitMQ status
  • MinIO/S3 connectivity
  • Redis cluster status

5. Functional testing

  1. Platform Login

    • Verify default admin credentials work
    • Test SSO if configured

  2. Data Operations

    • Create a test entity
    • Import a sample STIX bundle
    • Verify connectors are working

  3. Integration Testing

    • Test configured connectors
    • Verify data ingestion
    • Check export functionality

6. Upgrade testing

# Test upgrade from previous version
helm upgrade openaev-test charts/openaev --namespace openaev-test

7. Clean-up

# Remove test deployment
helm uninstall openaev-test --namespace openaev-test
kubectl delete namespace openaev-test

Automated testing

For CI/CD pipelines, you can use the following tools:

  1. Chart Testing
  2. Helm Unit Tests

Example CI test command:

ct lint-and-install --config ct.yaml