Integration test framework

[PrasadG193]

Change Overview

• Add helper methods in pkg/testutils to create Profile based on cred set as env vars
• Export kanctl helper methods for integration tests
• Add postgres rds integration test
• Add new make rule "make integration-test"
• Add support for AWS_SESSION_TOKEN in postgres test

Pull request type

Please check the type of change your PR introduces:

• 🚧 Work in Progress
• 🌈 Refactoring (no functional changes, no api changes)
• 🐹 Trivial/Minor
• 🐛 Bugfix
• 🌻 Feature
• 🗺️ Documentation
• 🤖 Test

Issues

• #XXX

Test Plan

• 💪 Manual
• ⚡ Unit test
• 💚 E2E

[SupriyaKasten]

@PrasadG193, I discussed your concerns with @tdmanv.
Regarding the func GetEnvOrSkip(c *check.C, varName string), we will have to modify the test interface in order to provide the c param and skip the test early, during setup, if the env variables are not set.

Regarding how to set up env variable in container: @tdmanv will discuss more about it in the next meeting. for now, you can assume that the env variable are set and move ahead accordingly. We are planning to run a new job in addition to the travis CI, to run these integration tests. more discussion will be done over the meeting. Lets make sure that the tests pass locally for you and please include the result of the test in the PR commit.

[PrasadG193]

@SupriyaKasten I've modified interfaces to pass check object and used that in error checking.
About test results, do we want to include the verbose output in the commit? Because it is too long (around 300 lines) for Postgres test. I am not sure if that would a good idea.

[PrasadG193]

E2E integration test verbose logs
Command: go test -v ./pkg/testing -tags=integration -timeout 30m
logs: https://gist.github.com/PrasadG193/3aa12a9d8fbd5febf323636cc365c4ce