AzureAD Functional Testing about scubagear HOT 5 CLOSED

When running the G3 With no variant, the AAD functional test fails for AAD-3.2v1
@tkol2022

from scubagear.

When running the G3 With no variant, the AAD functional test fails for AAD-3.2v1 @tkol2022

@schrolla @nanda-katikaneni @dagarwal-mitre I investigated this and this specific test scenario failure is to be expected at this time due to reasons that I will explain offline at the stand-up. The release should not be delayed due to this and this is not a bug in the AAD code.

from scubagear.

All other AAD functional tests were passed, here are the results:
AAD G5 No Variant:

AAD G5 Variant:

AAD E5 No Variant:

AAD E5 Variant:

AAD GCC High No Variant:

AAD GCC High Variant:

AAD G3 No Variant (error discussed above):

AAD G3 Variant:

from scubagear.

Noticed when running from PSGallery on all products, the links for the baselines document are not working and leading to a file not found, as well as the note within the AAD to the readme

from scubagear.

Noticed when running from PSGallery on all products, the links for the baselines document are not working and leading to a file not found, as well as the note within the AAD to the readme

This is a product of bumping the version before the release tag is created (at release time). If you want to validate that the report link will work, change the URL in the browser back to the last release (1.2.0) and verify the page still comes up. Once we release and the v1.3.0 tag is created, it'll work properly.

from scubagear.