You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to use Edge profiles for testing different user account types. When I am testing an SSO application like Salesforce or Microsoft, appropriate authentication will work when I right click the browser and run as the specific user.
However, when I get the user data folders from appdata and run with Serenity, I can see the profile is being used, but the authentication is being dropped and using the logged in user instead of the profile.
Why is the user-data-dir not being treated the same as run as?
What did you expect to happen?
I expect the profile and the run as to produce the same result and login to the browser as the user profile.
Serenity BDD version
3.7.1
JDK version
17
Execution environment
Windows 10
Edge v128
How to reproduce the bug.
Update serenity.conf Edge args user-data-dir to point to specific user
Run test and navigate to SSO page
Validate which use is signed in
How can we make it happen?
Work on this myself and propose a PR (with Serenity BDD team guidance)
The text was updated successfully, but these errors were encountered:
What happened?
I am attempting to use Edge profiles for testing different user account types. When I am testing an SSO application like Salesforce or Microsoft, appropriate authentication will work when I right click the browser and run as the specific user.
However, when I get the user data folders from appdata and run with Serenity, I can see the profile is being used, but the authentication is being dropped and using the logged in user instead of the profile.
Why is the user-data-dir not being treated the same as run as?
What did you expect to happen?
I expect the profile and the run as to produce the same result and login to the browser as the user profile.
Serenity BDD version
3.7.1
JDK version
17
Execution environment
Windows 10
Edge v128
How to reproduce the bug.
How can we make it happen?
Work on this myself and propose a PR (with Serenity BDD team guidance)
The text was updated successfully, but these errors were encountered: