The process for running production tests is the same as functional testing we executed earlier. The difference is in the tests we execute, not how we do it.

The goal of production tests is not to validate all the units of our application. Unit tests did that. It is not going to validate anything on the functional level. Functional tests did that. Instead, they are very light tests with a simple goal of validating whether the newly deployed application is correctly integrated with the rest of the system. Can we connect to the database? Can we access the application from outside the cluster (as our users will)? Those are a few of the questions we're concerned with when running this last round of tests.

The tests are written in Go, and we still have the golang container running. All we have to do it to go through the similar steps as before.

 1  kubectl -n go-demo-3-build 
 2      exec -it cd -c golang -- sh
 3
 4  export ADDRESS=$(cat prod-addr)

Now that we have the address required for the tests, we can go ahead and execute them.

 1  go test ./... -v --run ProductionTest

The output of the command is as follows.

=== RUN   TestProductionTestSuite
=== RUN   TestProductionTestSuite/Test_Hello_ReturnsStatus200
--- PASS: TestProductionTestSuite (0.10s)
    --- PASS: TestProductionTestSuite/Test_Hello_ReturnsStatus200 
(0.01s)
PASS
ok      _/go/go-demo-3  0.107s
  

Production tests were successful, and we can conclude that the deployment was successful as well.

All that's left is to exit the container before we clean up.

 1  exit