Skip to content

Conversation

@westin-m
Copy link
Contributor

@westin-m westin-m commented Sep 26, 2024

The following E2E scenarios were tested using the corresponding devapps:
Web app calls web api call graph
B2C web app calls web api
Owin
Blazer server calls web api
Blazer server B2C calls api
Ciam web app calls api
Web app calls graph
Deamon console calling downstream api, graph

All are working as expected.

@westin-m westin-m linked an issue Sep 26, 2024 that may be closed by this pull request
@westin-m westin-m marked this pull request as ready for review September 27, 2024 01:37
@westin-m westin-m requested a review from a team as a code owner September 27, 2024 01:37
Copy link
Collaborator

@jmprieur jmprieur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM at first review, @westin-m
Make sure you run end to end tests with credentials.
There was a race condition at some point, which is why the credential loaders used GetAwaiter.GetAsync().

I'm surprised there is no change in the public API?

Copy link
Collaborator

@jennyf19 jennyf19 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would like to have clarity on which E2E tests were run to verify things are working as expected, and which scenarios were covered.
would like to have no public API changes now.

@westin-m
Copy link
Contributor Author

would like to have clarity on which E2E tests were run to verify things are working as expected, and which scenarios were covered. would like to have no public API changes now.

I've added this to the description

This was referenced Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add threading analyzers and resolve issues

8 participants