[Identity] Browser tests

[HarshaNalluru]

Currently, the identity package doesn't have run the browser tests (echo skipped).
However, individual SDKs use ClientSecretCredential with disabled security in the browser through karma conf.

• We should find a way to test with the InteractiveBrowserCredential in the CI, and get rid of the ClientSecretCredential in our browser tests. (Also consider how the recorder would play in this scenario.)
• If we are relying on ClientSecretCredential for a longer period for testing in the browsers, we should add browser tests in the identity package similar to what we have in the individual SDKs to figure out the things that might break the browsers so that it would help find the regressions sooner than when we import the identity library in our SDKs. Reference - [Identity] Reverting ClientSecretCredential and UsernamePasswordCredential to v1 only for browsers, and fixing Karma browser bundles #14910

[KarishmaGhiya]

Refer this - https://github.com/sadasant/identity-browser-tests/blob/dev/AuthorizationCodeCredential/ideal.ts

[sadasant]

For context:

• Testing InteractiveBrowserCredential isn’t trivial with our current setup because the page that has Karma loaded needs to redirect to Azure, then come back, losing Karma’s state and potentially encountering other errors.
• In the link that Karishma shared above, I’m starting to test how to use “puppeteer” to test these interactive credentials.
  • Puppeteer (or other libraries, like Casper.js) allow Node.js to manage browser tabs. They follow through redirections.
  • Even if testing is viable with Puppeteer, we still need to figure out how to make it work nicely with our current testing infrastructure.

My current thoughts are that I could start playing with Puppeteer while I work on the new features for the browser experience for JS, and once we have a reliable experience there (separate from our SDK repo), we could present it to the team.

[github-actions]

Hi @HarshaNalluru, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.