Packaging tests

[TheRealPiotrP]

• Upgrade
• Remove
• Purge
• Install

Try to validate that the packages install a consistent payload.

[brthor]

Install, Purge, and Remove are included as tests in dotnet/cli#50 , will enable Upgrade tests when we have the bootstrapped version in the feed.

For validating the package payload I have the following proposal.

There is an integration_tests folder in the directory structure of #4303. This folder should contain basic tests indicating that the surface area of the install is consistent. The flow of execution would look like this:

1. package_tool is called on the package layout folder
2. .deb, integration_test directory, and test.sh are placed in the output folder
3. test.sh is called and performs install, purge, remove, upgrade tests
4. test.sh installs the package
5. test.sh calls all tests in integration_tests directory
6. test.sh removes the package

Thoughts @piotrpMSFT @Sridhar-MS ?

[brthor]

E2E Tests for the deb package are tracked here dotnet/cli#381

Let's use this issue to track finishing upgrade tests.