diff --git a/chart/templates/minio/minio/values.yaml b/chart/templates/minio/minio/values.yaml
index 590d34af8b0484ab7c6ef1efb3e08333c243ce8b..45995002c5ca7d61ee8073aa2b3b9d2656491fed 100644
--- a/chart/templates/minio/minio/values.yaml
+++ b/chart/templates/minio/minio/values.yaml
@@ -18,4 +18,7 @@ podAnnotations:
   traffic.sidecar.istio.io/includeInboundPorts: "*"
   traffic.sidecar.istio.io/excludeInboundPorts: "9443"
 
+imagePullSecrets:
+  - name: private-registry
+
 {{- end -}}
diff --git a/charter/PackageRequirements.md b/charter/PackageRequirements.md
index 79135440d5799b97440409a5f61b46ecd9c73956..2493a1c490c52e41bc1e45ec0e60d3a18c3b3567 100644
--- a/charter/PackageRequirements.md
+++ b/charter/PackageRequirements.md
@@ -92,6 +92,8 @@ The common components that each package will have are defined in the following f
 ├── tests/
     ├── cypress             # folder containing e2e tests using the cypress test framework
 ├── chart/                  # Folder containing helm chart
+    ├── templates           # folder helm chart templates
+      ├── tests             # folder containing helm chart tests 
 ```
 
 ## PR-X. CI/CD pipeline is required for each Big Bang Package
diff --git a/charter/Testing.md b/charter/Testing.md
index 26dc6fad048941faba90347aea65ad75a87b6eb7..d8541b3e544ebcf3a50d54642219d57144c9c830 100644
--- a/charter/Testing.md
+++ b/charter/Testing.md
@@ -6,6 +6,7 @@ There are multiple phases of testing for an application to get into a customer e
 
 * New Iron Bank Image
 * Changes to Manifests for deployments
+* Helm Chart Tests to verify operation within the cluster
 * Newly supported configurations of application
 
 ## Testing Platform
@@ -36,6 +37,52 @@ Each "Test" scenario will contain the following information:
 
 The Smoke tests will be run internal on the Kubernetes cluster via a Job.  The testing framework will inject a configuration object provided in the repo as a configmap for the job and run the job, ensure its successful, and provide the logs back to the user CI/CD pipeline for review.
 
+### Helm Chart Testing
+
+The Big Bang application pipelines have the ability to execute one or more [Helm Chart tests](https://helm.sh/docs/topics/chart_tests)
+after a chart has been deployed to the cluster.  Helm tests deploy one or more pods/containers and any other supporting
+kubernetes objects in order to verify that the application is operational.
+  
+For example, the  Minio instance package has additional CLI testing capabilities via the use of Helm Chart Tests.  These
+tests invoke the MC command line tool to create, delete, populate, and retrieve information from Minio buckets.  Examples of
+other types of Helm Chart Tests including:
+
+* Validate that your configuration from the values.yaml file was properly injected.
+* Make sure your username and password work correctly for the configuration
+* Use CLI or API tests to access the application
+
+The package pipelines have been enhanced to execute the "helm test" command and dump the log files of the tests results.
+
+In order to add Helm Chart tests to your application, the following enhancements need to be made to the Helm Chart.
+
+* A test directory is added to templates/ directory within the helm chart.  This directory contains Kubernetes object
+definitions which are deployed only when a "helm Test" command is executed.  As an example, tests can be YAML files that
+execute pods with containers, deply config maps, secrets, or other objects.
+* When a files contain a pod / container defintion that executions tests, the container must return success or failure
+(i.e., the container should exit successfully with an exit 0 for a test to be considered a success).
+* Each test object defintion must contain a "helm.sh/hook: test-success" annotation telling Helm that this object is a
+test and should only be deployed when tests are executed. The following example create a configmap that is only
+created during testing.
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: "{{ .Release.Name }}-cypress-test-configmap"
+  annotations:
+    "helm.sh/hook": test-success
+    "helm.sh/hook-weight": "5"
+    sidecar.istio.io/inject: "false"
+  labels:
+    helm-test: enabled
+    {{- include "minio.labels" . | nindent 4 }}
+  namespace: {{ .Release.Namespace }}
+data:
+{{ (.Files.Glob "cypress/*").AsConfig | indent 2 }}
+
+```
+Also note that the "helm.sh/hook-weight" can be used to order the creation and execution of test objects.
+
 ## Umbrella Testing
 
 The end consumable is the [Umbrella Application](Umbrella.md).  As new versions of Big Bang Applications become available, those changes need to be integrated into the Umbrella and tested.  Each Merge Request into the Umbrella Repo requires passing of an [Upgrade Tests](#upgrade-tests) and the [End to End Tests](#end-to-end-tests) for all mock environments.