Update tests for Policy SDK version 2018-03-01

[mentat9]

Description

NOTE: This update does NOT include a swagger change. Consequently, the below boxes for updating generate.cmd/generate.ps1 and project versions are not checked.

This update adds tests to cover the most recent update to the Governance Policy swagger.

Current REST spec for Governance Policy is here:
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/resources/resource-manager/Microsoft.Authorization/stable/2018-03-01
Most recent changes were in this PR:
Azure/azure-rest-api-specs#3032

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• Please add REST spec PR link to the SDK PR
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[dsgouda]

@mentat9 Please fix the failing managementgroup tests. You may have to re-record the tests

[dsgouda]

Please regenerate the code using the generate.ps1 here
Please commit all the files generated/modified

[mentat9]

Please regenerate the code using the generate.ps1 here

Is it normal to do a regeneration when there is no swagger change?

[dsgouda]

@mentat9 I assumed you were adding changes to the SDK too. Please disregard the regeneration

[mentat9]

@mentat9 Please fix the failing managementgroup tests. You may have to re-record the tests

Thing is, those aren't my tests and they don't record successfully on my machine. Playback, OTOH is working fine, so I don't understand why they aren't working on the server. Any ideas?

[mentat9]

@dsgouda, the tests have been re-recorded, but they still fail in the server build. Neither I nor Raj (the test owner) know how to fix this break. These tests all run fine locally in both of our dev environments. Can you help?

[dsgouda]

@mentat9 taking a look

[mentat9]

@dsgouda did you learn anything about the break?

[dsgouda]

Tried re-running the build without success, will have to debug myself. @shahabhijeet could you take a look at it too?

[dsgouda]

@mentat9 Please check if you copied over the recorded test into the SessionRecords directory.
You can use this script too.

[shahabhijeet]

@rajshah11 can you review this PR.

[rajshah11]

@dsgouda @shahabhijeet LGTM. I also ran the tests again and the changes made to ManagementGroups.Test project were fine. The build ran fine locally. Not sure why the build is failing here though.

[mentat9]

I think I might have figured it out. It looks like someone left behind some old unused test recordings under:

... \SDKs\Resource\Resource.Tests\SessionRecords\ResourceGroups.Tests.LiveManagementGroupsTests

When the management group SDK was removed from the resources SDK, these should have been deleted. I'm guessing server test discovery is finding these and trying to run them, but they are outdated.

Hopefully, that is the problem. If so, I don't understand why my build was the first to break. I would have expected every build since the MG code was removed from the Resource SDK should have broken.

[mentat9]

I have no idea what this failure in the Travis build means:

"The command "sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 417A0893" failed and exited with 2 during ."

But I've seen it before and it had nothing to do with my PR: it was something broken in the build environment. @dsgouda (or someone), can you force a retry on the Travis build?

[dsgouda]

LGTM