Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FunctionalTestUtils LoadProviderExport loads incorrect file #1333

Closed
schrolla opened this issue Sep 24, 2024 · 0 comments · Fixed by #1334
Closed

FunctionalTestUtils LoadProviderExport loads incorrect file #1333

schrolla opened this issue Sep 24, 2024 · 0 comments · Fixed by #1334
Assignees
Labels
bug This issue or pull request addresses broken functionality
Milestone

Comments

@schrolla
Copy link
Collaborator

🐛 Summary

During functional testing, when using modified config file, the LoadProviderExport private function from the FunctionalTestUtils.ps1 script is used to load that modified config file, but the current version loads the original rather than the modified config.

To reproduce

Steps to reproduce the behavior:

  1. Run a testplan that uses UpdateProviderExport in its preconditions and updates a value to make the test pass when it would normally fail. Specifically, you can run the existing MS.AAD.3.1v1 and MS.AAD.3.2v1 tests.
  2. Note that the test will fail anyway.

Expected behavior

I expected the tests to pass based on the configured cached settings.

Any helpful log output or screenshots

Shows the regression in the code from the previous working version (right) to the bugged version (left)
image

@schrolla schrolla added the bug This issue or pull request addresses broken functionality label Sep 24, 2024
@schrolla schrolla added this to the Jellyfish milestone Sep 24, 2024
@schrolla schrolla self-assigned this Sep 24, 2024
@schrolla schrolla linked a pull request Sep 24, 2024 that will close this issue
20 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue or pull request addresses broken functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant