[COMPASS-5178] Create an e2e test case that checks that latest changes in Compass don't cause keychain access issues when applied on top of latest GA Created: 15/Oct/21  Updated: 13/Dec/23  Resolved: 13/Dec/23

Status: Closed
Project: Compass
Component/s: CI, Tech debt
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Sergey Petushkov Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: COMPASS-6856
Documentation Changes: Not Needed
Sprint: Iteration Qantassaurus

 Description   

We want to make sure that every time we make an update to Compass, when we apply it as an update to latest Compass release in corresponding channel (e.g., we made a change in main branch that corresponds to the dev release channel, when we apply it on top of previous Compass build generated in main branch) it doesn't prompt user for the keychain access.

For that we want to add an e2e test that first finds the latest release for the channel (dev, beta, or ga), runs the app and stores a connection in favorites. After that we "update" the app with the build made from the latest source and check that the app works and doesn't prompt for the keychain password.



 Comments   
Comment by Basit Chonka [ 13/Dec/23 ]

As this point we migrated to the usage of safeStorage that electron offers and we are not triggering OS keychain directly. Even if user is prompted to unlock the keychain, it will only be once and not many times.

Manually testing it suffices in this case.

Generated at Wed Feb 07 22:38:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.