Add functionality to see testing coverage

[michaelhilborn]

No description provided.

[Pseusco]

I'm not sure about the HEAD sections of this PR

[akuljos]

Looks good! I think, though, that for the DNS/Edge Function tests, it might be a good idea to have additional unit tests for if the user inputs 'n', just to ensure that the resources aren't being deleted when that option is specified.

[michaelhilborn]

Looks good! I think, though, that for the DNS/Edge Function tests, it might be a good idea to have additional unit tests for if the user inputs 'n', just to ensure that the resources aren't being deleted when that option is specified.

Changes made to address this in commit 9bf54a0

[akuljos]

The failed Travis test is due to some inconsistencies between the master branch and testing branch in regards to a positional variable in the initialization of the SecretCertificateCreator object within my testing file. When I have that positional variable, it errors out due to the lack of that positional variable in the testing branch; when I don't have that positional variable, it errors out due to the presence of the positional variable in the master branch. This change shouldn't affect our functionality in any way and it should be resolved once the pull request is merged.