Silverfish/proton-bridge
1
0
Fork 1
mirror of https://github.com/ProtonMail/proton-bridge.git synced 2025-12-15 14:56:42 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

feat(GODT-2556): Add functional test for Heartbeat Init and telemetry availability.

Browse Source
This commit is contained in:
Romain LE JEUNE
2023-04-21 10:06:01 +02:00
committed by Romain Le Jeune
parent 4adc6d60b9
commit d3fc9a50f6
8 changed files with 150 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

85
tests/features/bridge/heartbeat.feature
View File

@ -4,7 +4,7 @@ Feature: Send Telemetry Heartbeat
And bridge starts
Scenario: Send at first start - one user
Scenario: Send at first start - one user default settings
Then bridge telemetry feature is enabled
And bridge needs to send heartbeat
When the user logs in with username "[user:user1]" and password "password"
@ -37,6 +37,89 @@ Feature: Send Telemetry Heartbeat
"""
And bridge do not need to send heartbeat
Scenario: Send at first start - one user modified settings
Then bridge telemetry feature is enabled
And bridge needs to send heartbeat
When the user has disabled automatic updates
And the user has disabled automatic start
And the user has enabled alternative routing
And the user hides All Mail
And the user set IMAP mode to SSL
And the user set SMTP mode to SSL
And the user changes the IMAP port to 42695
And the user changes the SMTP port to 56942
And the user changes the gluon path
And the user changes the default keychain application
When the user logs in with username "[user:user1]" and password "password"
And user "[user:user1]" finishes syncing
Then bridge eventually sends the following heartbeat:
"""
{
"MeasurementGroup": "bridge.any.usage",
"Event": "bridge_heartbeat",
"Values": {
"nb_account": 1
},
"Dimensions": {
"auto_update": "off",
"auto_start": "off",
"beta": "off",
"doh": "on",
"split_mode": "off",
"show_all_mail": "off",
"imap_connection_mode": "ssl",
"smtp_connection_mode": "ssl",
"imap_port": "custom",
"smtp_port": "custom",
"cache_location": "custom",
"keychain_pref": "custom",
"prev_version": "0.0.0",
"rollout": 42
}
}
"""
And bridge do not need to send heartbeat
Scenario: Send at first start - one user telemetry disabled
Then bridge telemetry feature is enabled
And bridge needs to send heartbeat
When the user disables telemetry in bridge settings
And the user logs in with username "[user:user1]" and password "password"
And user "[user:user1]" finishes syncing
And bridge needs to send heartbeat
Then the user sets the address mode of user "[user:user1]" to "split"
And the user enables telemetry in bridge settings
Then bridge eventually sends the following heartbeat:
"""
{
"MeasurementGroup": "bridge.any.usage",
"Event": "bridge_heartbeat",
"Values": {
"nb_account": 1
},
"Dimensions": {
"auto_update": "on",
"auto_start": "on",
"beta": "off",
"doh": "off",
"split_mode": "on",
"show_all_mail": "on",
"imap_connection_mode": "starttls",
"smtp_connection_mode": "starttls",
"imap_port": "default",
"smtp_port": "default",
"cache_location": "default",
"keychain_pref": "default",
"prev_version": "0.0.0",
"rollout": 42
}
}
"""
And bridge do not need to send heartbeat
Scenario: GroupMeasurement rejected by API
Given heartbeat is not whitelisted
Then bridge telemetry feature is enabled