Test/integrations

[kiran-chaudhary]

Added setup for integration tests.

[antazoey]

These are good!

[alanag13]

@kiran-chaudhary I was thinking about an approach this sort of like this:

• create profile reading profile details from environment, if it does not already exist.
• test execution.

Note that I am skipping the "delete all profiles" and "delete profile as part of cleanup activity" steps. This would allow us to set environment variables on our local machines for accounts that we already have profiles for to run these tests locally without having the profiles get deleted.
We could use this functionality in our CI as well -- the github actions are run on containers that get destroyed at the end of the run, so we would be creating the profile new every time.

Check out the bottom of this file:
https://github.com/code42/c42eventextractor/blob/master/.github/workflows/build.yml

and this one:
https://github.com/code42/c42eventextractor/blob/master/run_integrations.py

to see how I set this up for c42eventextractor.

One thing that occurs to me is that in order to make this automatable, we would need to add (optional) flags that allow us to skip confirmation prompts, and that allow for the password to be input as part of the create-profile command. Those should probably be their own tasks, I'll get stories created for them.

[kiran-chaudhary]

Used pexpect module to pass password on prompt.

[alanag13]

@kiran-chaudhary FYI I will usually assume that PRs that are marked as draft are not considered ready by the author, (except immediately after opening and asking for initial feedback), so be sure to mark them as ready for review.

Just one small note about using os.remove instead of rm -f but this looks good. We would want commands to handle creating profiles but that can be done in a separate PR.

[kiran-chaudhary]

@kiran-chaudhary FYI I will usually assume that PRs that are marked as draft are not considered ready by the author, (except immediately after opening and asking for initial feedback), so be sure to mark them as ready for review.

Just one small note about using os.remove instead of rm -f but this looks good. We would want commands to handle creating profiles but that can be done in a separate PR.

Sorry I missed changing back to ready for review.